Hostname
qvc.jp
Last fetched
qvc.jp resolves to 2.23.244.21, announced in 2.23.244.0/22 by AKAMAI-AS - Akamai Technologies, Inc. in DE. qvc.jp is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 2.23.244.21
2.23.244.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.215.121.89
23.215.120.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Hamburg, DE
- 23.37.193.71
23.37.192.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
- 23.58.109.79
23.32.0.0/11 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.62.10.18
23.62.10.0/23 · AKAMAI-AS - Akamai Technologies, Inc. · Secaucus, US
- 23.75.65.68
23.75.64.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Prague, CZ
- 23.195.248.15
23.195.248.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Prague, CZ
- 2.19.216.18
2.19.216.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Prague, CZ
IPv6 resolution
No AAAA record for qvc.jp is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrant organisation
- thomson reuters professional kk. thomson brandy
- Contact emails
- domain_names@qvc.com, admin@thomsonbrandy.jp
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
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
SPF policy
- exists: %{i}._i.%{d}._d.espf.dmp.cisco.com
- include: %{d}.b0.spf-protect.dmp.cisco.com
Threat-feed evidence
History
Related pages
Pivot from qvc.jp 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.jp"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.