Skip to content

Hostname

angonet.org

Last fetched

angonet.org resolves to 104.193.174.145, announced in 104.193.174.0/23 by IDIGITAL - Idigital Internet Inc. in CA. angonet.org 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 · angonet.orgRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/angonet.org

Resolution chain

IPv6 resolution

No AAAA record for angonet.org is recorded in WhisperGraph.

Attribution

idigital

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
dz96k8pf9gn@networksolutionsprivateregistration.com, n64qt2j28gp@networksolutionsprivateregistration.com, un3uw88e3pa@networksolutionsprivateregistration.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

  • ns396.canadianwebhosting.com
  • ns397.canadianwebhosting.com
  • emily.ns.cloudflare.com
  • rodney.ns.cloudflare.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

  • angonet.org
  • _dc-mx.fc28b4e45a7a.angonet.org

SPF policy

  • ip: 64.34.111.235/32
  • ip: 64.34.111.239/32
  • ip: 64.34.111.253/32
  • a: angonet.org
  • mx: angonet.org
  • ip: 104.193.174.145

Threat-feed evidence

History

Related pages

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