Skip to content

Hostname

diyworld.com

Last fetched

diyworld.com resolves to 119.91.109.253, announced in 119.91.64.0/18 by TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited in CN. diyworld.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 · diyworld.comRouting diversity1.5/10Peering density4.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/diyworld.com

Resolution chain

IPv6 resolution

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

Attribution

shenzhen tencent computer

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of diyworld.com owner
Contact emails
polo@diyworld.com, 111b8445-df8c-4454-aa22-8592af61159d@identity-protect.org, 16233ed4-2314-46a6-8a95-7cf64030d225@identity-protect.org, 79b92c90-ad9d-4728-ac93-01326d6fa924@identity-protect.org, 93702965-e266-4f5a-b462-2ac193491c33@identity-protect.org, a6cb089e-be58-425b-950a-907ef0fcda21@identity-protect.org, ec0da645-38a3-43c2-9401-f48f703c4977@identity-protect.org

Subdomains

Mail and authentication

Nameservers

  • ns-346.awsdns-43.com
  • ns1.diyworld.com
  • ns2.diyworld.com
  • ns-658.awsdns-18.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-1244.awsdns-27.org
  • ns-1693.awsdns-19.co.uk

MX records

  • inbound-smtp.us-west-2.amazonaws.com
  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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