Skip to content

Hostname

zooeco.com

Last fetched

zooeco.com resolves to 5.45.124.195, announced in 5.45.124.0/24 by PAGM-AS - CLOUD.DOG OU in EE. zooeco.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 · zooeco.comRouting diversity2.4/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.4/10canon.whisper.security/host/zooeco.com

Resolution chain

IPv6 resolution

Attribution

dog ou

ORIGIN_AS

WHOIS identity

Registrar
iana:1426
Registrant organisation
personal data, can not be publicly disclosed according to applicable laws.
Contact emails
genstap67@gmail.com, zooeco@gmail.com, e-igo@ukr.net, zooeco.com@r01.whoisproxy.ru

Subdomains

Subdomain
info.zooeco.com
mail.zooeco.com
www.zooeco.com

Showing 3 of 4. 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

Mail and authentication

Nameservers

  • dns.fastdns24.com
  • dns3.fastdns24.eu
  • dns4.fastdns24.link
  • 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
  • dns2.dns-root.org
  • dns2.fastdns24.org
  • dns3.dns-root.pro
  • dns1.dns-root.ru
  • ns1.hostiman.ru
  • ns2.hostiman.ru
  • ns3.hostiman.ru
  • ns4.hostiman.ru
  • ruvip66.hostiman.ru

MX records

  • mail.zooeco.com

SPF policy

  • a: zooeco.com
  • mx: zooeco.com
  • ip: 2a00:ab00:1103:7:66:0:0:1

Threat-feed evidence

History

Related pages

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