Hostname
dhdt.net
Last fetched
dhdt.net resolves to 162.210.196.167, announced in 162.210.192.0/21 by LEASEWEB-USA-WDC - Leaseweb USA, Inc. in US. dhdt.net is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 162.210.196.167
162.210.192.0/21 · LEASEWEB-USA-WDC - Leaseweb USA, Inc. · Ashburn, US
- 216.245.197.42
216.245.192.0/19 · LIMESTONENETWORKS - Limestone Networks, Inc. · Dallas, US
- 216.245.197.46
216.245.192.0/19 · LIMESTONENETWORKS - Limestone Networks, Inc. · Dallas, US
- 77.247.179.82
77.247.176.0/21 · NFORCE - NForce Entertainment B.V. · Roosendaal, NL
- 77.247.179.85
77.247.176.0/21 · NFORCE - NForce Entertainment B.V. · Roosendaal, NL
- 77.247.179.89
77.247.176.0/21 · NFORCE - NForce Entertainment B.V. · Roosendaal, NL
- 77.247.179.91
77.247.176.0/21 · NFORCE - NForce Entertainment B.V. · Roosendaal, NL
- 78.157.209.172
78.157.208.0/20 · UKSERVERS-AS - UK Dedicated Servers Limited · London, GB
- 95.211.136.187
95.211.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
IPv6 resolution
No AAAA record for dhdt.net is recorded in WhisperGraph.
Attribution
leaseweb usa
ORIGIN_AS
WHOIS identity
Subdomains
Showing 5 of 5 subdomains (5 per page).
Mail and authentication
Nameservers
- ns1.badgerdns.com
- ns2.badgerdns.com
- ns1.hostresolver.com
- ns1.milesmx.com
- ns2.milesmx.com
- ns1.quokkadns.com
- ns1.wombatdns.com
- ns2.wombatdns.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
Threat-feed evidence
History
Related pages
Pivot from dhdt.net 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: "dhdt.net"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.