Skip to content

Hostname

whendu.com

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
alexander prokopyev
Contact emails
xana4ok@gmail.com, a175ce94409940fa46329802bb48110d-1840386@contact.gandi.net, 059fe66e-bfce-40a5-8799-3682033a5640@identity-protect.org, 549726a6-97e9-4a37-bc97-de1f28335e91@identity-protect.org, 82ded25a-2d15-444b-8216-1b8c0827e555@identity-protect.org, 8fe55192-7a44-4777-b5b8-1a4793462311@identity-protect.org, 9a21cee6-460b-4223-b3e4-12bfd9606ea8@identity-protect.org, d743a662-78dd-4caa-aa40-aff7936897e4@identity-protect.org

Subdomains

Mail and authentication

Nameservers

  • ns-91.awsdns-11.com
  • ns-700.awsdns-23.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-1098.awsdns-09.org
  • ns-1844.awsdns-38.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.mandrillapp.com

Threat-feed evidence

History

Related pages

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