Skip to content

Hostname

destroyhistory.com

Last fetched

destroyhistory.com resolves to 104.21.69.234, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. destroyhistory.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 · destroyhistory.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/destroyhistory.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1923
Registrant organisation
john allison
Contact emails
scarygoround@gmail.com

Subdomains

Subdomain
mail.destroyhistory.com

Showing 1 of 1 subdomain (1 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

  • alex.ns.cloudflare.com
  • lola.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

SPF policy

  • include: auralink.it.com
  • ip: 149.50.132.158
  • ip: 168.197.49.212
  • ip: 171.22.183.97
  • ip: 178.170.102.169
  • ip: 185.226.92.159
  • ip: 185.246.87.21
  • ip: 193.109.120.111
  • ip: 200.58.100.216
  • ip: 200.58.100.225
  • ip: 200.58.100.235
  • ip: 200.58.100.51
  • ip: 200.58.100.54
  • ip: 200.58.103.85
  • ip: 200.58.107.225
  • ip: 5.135.14.84
  • ip: 66.70.200.164
  • ip: 66.70.200.170
  • ip: 74.50.118.238
  • ip: 93.127.181.62

Threat-feed evidence

History

Related pages

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