Skip to content

Hostname

burberry.com

Last fetched

burberry.com resolves to 5 IPv4 addresses operated by AKAMAI-AS - Akamai Technologies, Inc. in US.

Nutrition Label

WHISPER CANON · burberry.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/burberry.com

Resolution chain

burberry.com resolves to 5 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
104.81.170.201104.81.160.0/20AS16625AKAMAI-AS - Akamai Technologies, Inc.US
23.201.167.6323.201.160.0/19AS16625AKAMAI-AS - Akamai Technologies, Inc.US
23.210.112.20723.210.112.0/20AS16625AKAMAI-AS - Akamai Technologies, Inc.DE
23.215.16.18723.215.16.0/21AS16625AKAMAI-AS - Akamai Technologies, Inc.DE
23.56.201.18423.56.200.0/21AS16625AKAMAI-AS - Akamai Technologies, Inc.DE

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from burberry.com in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

24 SPF mechanisms authorising senders for burberry.com.

MechanismTarget
SPF_Asr-mx-app-01-brb.sparkred.com
SPF_INCLUDE_shortspf.launchmetrics.com
SPF_INCLUDE_spf-dc12.successfactors.com
SPF_INCLUDEamazonses.com
SPF_INCLUDEspf.protection.outlook.com
SPF_INCLUDEspf1.burberry.com
SPF_INCLUDEspf2.burberry.com
SPF_INCLUDEspf3.burberry.com
SPF_IP155.56.220.129/32
SPF_IP155.56.221.13/32
SPF_IP155.56.221.14/32
SPF_IP165.72.200.96
SPF_IP192.40.173.140/31
SPF_IP193.67.137.10
SPF_IP193.67.137.72
SPF_IP194.37.255.29/32
SPF_IP217.57.1.50
SPF_IP31.222.128.143
SPF_IP62.22.37.135
SPF_IP62.22.37.164
SPF_IP62.22.37.178
SPF_IP85.158.143.242/32
SPF_IP91.198.224.29/32
SPF_IP92.52.113.168

Related pages

Pivot deeper into the graph from burberry.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

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

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