Skip to content

Hostname

zerohash.com

Last fetched

zerohash.com resolves to 104.18.41.129, announced in 104.18.41.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. zerohash.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 · zerohash.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/zerohash.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of zerohash.com owner
Contact emails
infra@zerohash.com, justink1973@gmail.com, 0c9c750b-49f9-4b66-b851-0049cf294c0e@identity-protect.org, 0fb96957-3659-48d5-a55d-1c162591fa5d@identity-protect.org, 9718ae5d-55ad-4d74-b4f7-add14a0b02b0@identity-protect.org, b6cf4078-6b82-453f-a527-32f5b667e6cf@identity-protect.org, owner-3369031@zerohash.com.whoisprivacyservice.org, owner-3845914@zerohash.com.whoisprivacyservice.org, owner-6696395@zerohash.com.whoisprivacyservice.org, owner-8253074@zerohash.com.whoisprivacyservice.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

  • charles.ns.cloudflare.com
  • tricia.ns.cloudflare.com

MX records

  • usb-smtp-inbound-1.mimecast.com
  • usb-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: usb._netblocks.mimecast.com
  • include: _spf.salesforce.com
  • include: stspg-customer.com
  • include: mail.zendesk.com
  • include: 49109580.spf01.hubspotemail.net

Threat-feed evidence

History

Related pages

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