Skip to content

Hostname

dt.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1479
Registrant organisation
registration privacy, no-ip.com
Contact emails
cdesimone@dt.com, 0e3c3ea0b7439eb0-558210@privacy.no-ip.com, 175d8361357579d8-558210@privacy.no-ip.com, 1e027840711905a5-558210@privacy.no-ip.com, 39b596b76b84666e-558210@privacy.no-ip.com, 5a0de70af66a2084-558210@privacy.no-ip.com, 754bf388fe704f81-558210@privacy.no-ip.com, 812cfd49839c587c-558210@privacy.no-ip.com, 8ca67a1b0352e01b-558210@privacy.no-ip.com, 918a9667c523f564-558210@privacy.no-ip.com, 9b757c02611aef6b-558210@privacy.no-ip.com, bab7d499710dd27f-558210@privacy.no-ip.com, c6b20f009150c0fb-558210@privacy.no-ip.com, cb383af9245ec7d9-558210@privacy.no-ip.com, cd63bb449bd61423-558210@privacy.no-ip.com, d8c62fcf4458c0d1-558210@privacy.no-ip.com, daa946995e7a8910-558210@privacy.no-ip.com, ff91cd730fa60680-558210@privacy.no-ip.com, pwp-c4ecaeb76b78c813746de4fdcb3a0130@privacyguardian.org

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

  • lex.ns.cloudflare.com
  • marge.ns.cloudflare.com

MX records

  • d261500a.ess.barracudanetworks.com
  • d261500b.ess.barracudanetworks.com

SPF policy

  • include: _s83499928.fdmarc.net

Threat-feed evidence

History

Related pages

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