Skip to content

Hostname

dyson.dk

Last fetched

dyson.dk resolves to 162.159.142.173, announced in 162.159.128.0/19 by CLOUDFLARENET - Cloudflare, Inc. in CA. dyson.dk 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

WHISPER CANON · dyson.dkRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.0/10canon.whisper.security/host/dyson.dk

Resolution chain

IPv6 resolution

No AAAA record for dyson.dk is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:csc digital brand service, inc
Registrant organisation
dyson
Contact emails
domainnames@dyson.com

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
  • a4-67.akam.net
  • a9-67.akam.net
  • blue.foundationdns.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • blue.foundationdns.org

MX records

  • dyson-dk.mail.protection.outlook.com

SPF policy

  • include: _spf-a.dyson.com
  • include: _spf-b.dyson.com
  • include: _spf-d.dyson.com
  • include: _spf-edge-az.dyson.com
  • include: spf.protection.outlook.com
  • include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email

Threat-feed evidence

History

Related pages

Pivot from dyson.dk 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.dk"})-[: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.