Skip to content

Hostname

dyson.in

Last fetched

dyson.in resolves to 104.69.222.91, announced in 104.69.222.0/24 by AKAMAI-ASN1 - Akamai International B.V. in SE. dyson.in 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.inRouting diversity2.4/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.6/10canon.whisper.security/host/dyson.in

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:299
Registrant organisation
domain administrator
Contact emails
domainnames@dyson.com

Subdomains

Subdomain
admin.dyson.in
e.dyson.in
gtm.dyson.in
registration.dyson.in
saa.dyson.in
staging.dyson.in
support.dyson.in
track.dyson.in
www.dyson.in

Showing 9 of 14. 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.

Sample inbound links

Sample outbound links

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
  • blue.foundationdns.org

MX records

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

SPF policy

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

Threat-feed evidence

History

Related pages

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