Hostname
dyson.com.mx
Last fetched
dyson.com.mx resolves to 184.51.149.18, announced in 184.51.148.0/23 by AKAMAI-ASN1 - Akamai International B.V. in US. dyson.com.mx 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
- 184.51.149.18
184.51.148.0/23 · AKAMAI-ASN1 - Akamai International B.V. · Secaucus, US
- 184.51.149.49
184.51.148.0/23 · AKAMAI-ASN1 - Akamai International B.V. · Secaucus, US
- 23.196.227.102
- 23.196.227.108
- 23.36.162.206
23.36.162.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.36.162.214
23.36.162.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.36.162.220
23.36.162.0/24 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 172.66.2.168
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 162.159.142.172
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for dyson.com.mx is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dyson.com.mx. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Showing 5 of 10. 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
- blue.foundationdns.com
- a1-82.akam.net
- a13-64.akam.net
- a2-65.akam.net
- a24-65.akam.net
- a9-67.akam.net
- blue.foundationdns.net
- blue.foundationdns.org
MX records
- mail.dyson.com.mx
Threat-feed evidence
History
Related pages
Pivot from dyson.com.mx 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: "dyson.com.mx"})-[: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.