Hostname

qvc.it

Last fetched Mon, 21 Sep 2026 23:59:54 GMT

qvc.it resolves to 104.83.93.157, announced in 104.83.92.0/23 by SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A. in IT. qvc.it is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

104.83.93.157
104.83.92.0/23 · SEABONE-NET - TELECOM ITALIA SPARKLE S.p.A. · Palermo, IT
23.10.155.84
23.10.128.0/18 · AKAMAI-AS - Akamai Technologies, Inc. · Toronto, CA
23.201.252.223
23.201.240.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
23.63.118.65
23.63.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
23.67.128.219
23.67.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
23.67.131.86
23.67.128.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE

IPv6 resolution

No AAAA record for qvc.it is recorded in WhisperGraph.

Attribution

italia sparkle

ORIGIN_AS

WHOIS identity

Registrar: registrar:markmonitor international limited
Registrant organisation: general counsel

Subdomains

Subdomain
api.qvc.it
apps.qvc.it
blog.qvc.it
broadcast1.qvc.it
broadcast2.qvc.it
cdn.qvc.it
corporate.qvc.it
gyqbrs.qvc.it
identity.qvc.it
int-api.qvc.it
int-identity.qvc.it
int.qvc.it

Showing 12 of 61. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

ns3.qvc.com
a1-21.akam.net
a11-66.akam.net
a26-67.akam.net
a3-64.akam.net
a6-65.akam.net
a8-66.akam.net

MX records

mx1.hsn.iphmx.com
mx2.hsn.iphmx.com
qvc-it.mail.protection.outlook.com

SPF policy

exists: %{i}._i.%{d}._d.espf.dmp.cisco.com
include: %{d}.b0.spf-protect.dmp.cisco.com

Threat-feed evidence

History

Pivot from qvc.it into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "qvc.it"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.