Hostname
zoidial.com
Last fetched
zoidial.com resolves to 216.218.235.150, announced in 216.218.128.0/17 by HURRICANE - Hurricane Electric LLC in US. zoidial.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for zoidial.com is recorded in WhisperGraph.
Attribution
hurricane electric
ORIGIN_AS
WHOIS identity
- Registrar
- iana:93
- Registrant organisation
- eric thern
- Contact emails
- domains@zoidial.com.au, domains@zoidial.com, 130caf0aa5310b963e6c30d6f6048321a899c5ff@privatedomain.gkg.net, 1b21f6bfc435ceecde3208d71298c2c01aa65a90@privatedomain.gkg.net, 24b617cf92abea002909996980339601c24a42a4@privatedomain.gkg.net, 2df5febb4f79cd63306b7731f1dc6a8079d59ef6@privatedomain.gkg.net, 389cc625c982b4b7d2e20fe9daaa1df83f47dd2f@privatedomain.gkg.net, 7300c529f95db9ba7f66c8fde53b8a22e841a31f@privatedomain.gkg.net, 7d151aa5e7ef304eefecffc1a7968992f8134a30@privatedomain.gkg.net, a6e457c779c82bc796ec520f76428c6378c72c98@privatedomain.gkg.net, c34dd80f0e4fe79b7074d10c31d8c6a645c9d4fe@privatedomain.gkg.net, d2ba7c583d27b49558ff27e1fca9153d1530b7e8@privatedomain.gkg.net, f37fbc59f99f17cf75bd1df58cf2ebadd7fc25f9@privatedomain.gkg.net
Subdomains
Showing 12 of 69. View all subdomains →
Mail and authentication
Nameservers
- ns1.zoidial.com
- ns2.zoidial.com
- ns3.zoidial.com
- ns4.zoidial.com
- ns5.zoidial.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.us.ca2.zoidial.com
- mail.us.ca3.zoidial.com
- mail.zoidial.com
SPF policy
- a: zoidial.com
- mx: zoidial.com
- a: webserver.zoidial.com
Threat-feed evidence
History
Related pages
Pivot from zoidial.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: "zoidial.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.