Skip to content

Hostname

wherefour.com

Last fetched

wherefour.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. wherefour.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 · wherefour.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/wherefour.com

Resolution chain

No IPv4 resolution is recorded for wherefour.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:1068
Registrant organisation
matt brown
Contact emails
mattbrown2@yahoo.com, 293c895c5b9647f092dcd85694f0a8fb.protect@whoisguard.com, 7a05ebf95241467e90dc8aa51099f586.protect@whoisguard.com, 446d76bc350f443594e3144d9ddde806.protect@withheldforprivacy.com

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

  • ns-419.awsdns-52.com
  • ns-707.awsdns-24.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
  • ns-1286.awsdns-32.org
  • ns-1859.awsdns-40.co.uk

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: servers.mcsv.net

Threat-feed evidence

History

Related pages

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