Skip to content

Hostname

zeep.ly

Last fetched

zeep.ly resolves to 176.9.25.47, announced in 176.9.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. zeep.ly 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 · zeep.lyRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/zeep.ly

Resolution chain

IPv6 resolution

No AAAA record for zeep.ly is recorded in WhisperGraph.

Attribution

hetzner

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
registrar:libyan spider network (int)
Registrant organisation
jane m. hosford
Contact emails
jane80@protonmail.ch

Subdomains

Subdomain
com.zeep.ly
cpanel.zeep.ly
cpcalendars.zeep.ly
cpcontacts.zeep.ly
failed.zeep.ly
legacy.zeep.ly
mail.zeep.ly
ns1.zeep.ly
ns2.zeep.ly
old.zeep.ly
server2.zeep.ly
testing.zeep.ly

Showing 12 of 22. 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

  • ns1.netdynamics.gr
  • ns2.netdynamics.gr
  • 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
  • ns1.wondurl.org.uk
  • ns2.wondurl.org.uk

MX records

  • zeep.ly

SPF policy

  • a: zeep.ly
  • mx: zeep.ly
  • ip: 176.9.25.47

Threat-feed evidence

History

Related pages

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