Skip to content

Hostname

egpet.net

Last fetched

egpet.net resolves to 104.21.60.109, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. egpet.net 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 · egpet.netRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/egpet.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
domain admin
Contact emails
fb7cc5c6a26a4e02b25df6ac64d64446.protect@withheldforprivacy.com, admin@bnia.com.eg, contact@privacyprotect.org

Subdomains

Showing 4 of 4 subdomains (4 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

  • chance.ns.cloudflare.com
  • itzel.ns.cloudflare.com
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
  • dns1.registrar-servers.com
  • dns2.registrar-servers.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

  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • include: spf.web-hosting.com
  • a: egpet.net
  • mx: egpet.net
  • ip: 198.54.120.173
  • ip: 198.54.120.190
  • ip: 198.54.120.218
  • ip: 198.54.120.78

Threat-feed evidence

History

Related pages

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