Skip to content

Hostname

areafada.com

Last fetched

areafada.com resolves to 102.212.247.171, announced in 102.212.247.0/24 by Truehost Cloud Limited - Truehost Cloud Limited in KE. areafada.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 · areafada.comRouting diversity2.4/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/areafada.com

Resolution chain

IPv6 resolution

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

Attribution

truehost

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1509
Registrant organisation
domains by proxy,
Contact emails
areafada.com@domainsbyproxy.com, privacy@cosmotown.com

Subdomains

Showing 2 of 2 subdomains (2 per page).

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

  • ns1.cloudoon.com
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
  • ns2.cloudoon.net
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net
  • ns3.cloudoon.org

MX records

  • areafada.com
  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

SPF policy

  • a: areafada.com
  • mx: areafada.com
  • include: _spf.truehostcloud.com

Threat-feed evidence

History

Related pages

Pivot from areafada.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: "areafada.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.