Skip to content

Hostname

zeperfs.com

Last fetched

zeperfs.com resolves to 92.243.1.198, announced in 92.243.0.0/19 by GANDI-AS-2 - GANDI SAS in FR. zeperfs.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 · zeperfs.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/zeperfs.com

Resolution chain

IPv6 resolution

No AAAA record for zeperfs.com is recorded in WhisperGraph.

Attribution

gandi

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
jeannerot philippe
Contact emails
14e4hiitu7ik1qbctgkh@v.o-w-o.info, 70suyqnqezizo4ieizcg@r.o-w-o.info, acvbu1y2rqfh364v7hqg@d.o-w-o.info, fbqpnc8vnuzm0obam7m2@a.o-w-o.info, fn1bqsbh8cvnz6nou7h7@u.o-w-o.info, lajmxv5uxue2vnpr8xif@m.o-w-o.info

Subdomains

Subdomain
mail.zeperfs.com
www.zeperfs.com

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

Sample inbound links

Mail and authentication

Nameservers

  • dns103.ovh.net
  • ns103.ovh.net
  • 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.zeperfs.com

SPF policy

  • a: zeperfs.com
  • mx: zeperfs.com
  • a: mail.zeperfs.com
  • ip: 2001:4b98:dc0:41:216:3eff:fef9:2235
  • ip: 92.243.1.198

Threat-feed evidence

History

Related pages

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