Skip to content

Hostname

diecast.org

Last fetched

diecast.org resolves to 192.0.78.185, announced in 192.0.78.0/24 by AUTOMATTIC - Automattic, Inc in US. diecast.org 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 · diecast.orgRouting diversity1.5/10Peering density7.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/diecast.org

Resolution chain

IPv6 resolution

No AAAA record for diecast.org is recorded in WhisperGraph.

Attribution

automattic

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
gennera, knab &
Contact emails
fw4qy3qf79p@networksolutionsprivateregistration.com, gy32w3fp4mm@networksolutionsprivateregistration.com, hostmaster@genneraknab.com, t73ce8qe3vj@networksolutionsprivateregistration.com, uz7zw5rz86d@networksolutionsprivateregistration.com, wa9d258j8xe@networksolutionsprivateregistration.com, z23h75fu6zy@networksolutionsprivateregistration.com, zv7m695v53y@networksolutionsprivateregistration.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

  • ns1.wordpress.com
  • ns2.wordpress.com
  • ns3.wordpress.com

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
  • 75fdlq5hot2lyttxhlugqpfeisvrjix4ikgmq6bg2t2qsshxomua.mx-verification.google.com

SPF policy

  • include: _spf.google.com
  • include: _spf.wpcloud.com
  • ip: 209.18.98.224
  • ip: 209.18.98.225
  • ip: 67.231.156.76

Threat-feed evidence

History

Related pages

Pivot from diecast.org 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: "diecast.org"})-[: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.