Hostname
zeproc.com
Last fetched
zeproc.com resolves to 104.18.8.156, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. zeproc.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
- 104.18.8.156
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.9.156
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1910
- Registrant organisation
- on behalf of zeproc.com owner
- Contact emails
- zeproc.com@privatewho.is, 44a3e29c-0dbb-4fca-9cb0-efb065ff6fe8@identity-protect.org, a0e28dd7-6eff-494f-864f-a4c4fb8b231d@identity-protect.org, a428ec93-215f-47bd-ae33-a3094c47edd2@identity-protect.org, a810017a-976e-4cf9-ae3d-a8fc60f2a21d@identity-protect.org, eb847ae7-42d7-4534-b891-b66d020a7488@identity-protect.org, ed8b2cfc-a399-4fd4-b10e-e572f8bf8e7b@identity-protect.org
Subdomains
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
- gigi.ns.cloudflare.com
- micah.ns.cloudflare.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: mail.zendesk.com
- include: eu-sender.zohobooks.com
- include: eu.zcsend.net
Threat-feed evidence
History
Related pages
Pivot from zeproc.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: "zeproc.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.