Skip to content

Hostname

digitalairways.com

Last fetched

digitalairways.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. digitalairways.com 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 · digitalairways.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/digitalairways.com

Resolution chain

No IPv4 resolution is recorded for digitalairways.com in WhisperGraph.

IPv6 resolution

No AAAA record for digitalairways.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:74
Registrant organisation
franck lefevre
Contact emails
3823b7ebb7e78fa92b255f373c6d49aa-450106@contact.gandi.net, 602b3fb41268b14a8e9a9c95390fae5d-450106@contact.gandi.net, df4708bdfdfa7194863da8bd84bb607b-450106@contact.gandi.net

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

  • nsa.bookmyname.com
  • nsb.bookmyname.com
  • nsc.bookmyname.com
  • 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

MX records

  • mail.digitalairways.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • ip: 92.222.170.83

Threat-feed evidence

History

Related pages

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