CONTINUOUS INTERNET TELEMETRY24H DRIFT31,235 material changesacross 30,192 domains · 24h to ~12h ago · -6,787 vs yesterdayROTATION59 domains moved DNS from kirklanddc.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW556 curated domains not reachable+25 vs yesterdaySITE ERRORS33,775 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,602 sites429 rate-limit / 403 bot-block, a posture signal

dpt.com

Observed Jul 26, 2026, 00:55 UTC (12d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of dpt.com was taken 12d ago

dpt.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dpt.com under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch dpt.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 11:49 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat dpt.com actually stands on - every host below is a signed observation
dpt.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
dpt.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 5

  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns1.afternic.com dns.jomax.net

TLS Certificates (4)

Common NameIssuerExpires
dpt.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Sat, 16 Jan 2027 17:18:48 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000

Subdomains (0)

None observed.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_b9313c474c0e823e
Output Hash
3ef1b7778ccd49939fead2d9108bfbf1763b3467e510b22efa573b6aa407d6cb
Signature
ed25519:0c9c9e47fd3364e409e4a01a7b752b3b05516b668a867f8d600441f656950d9c0ca6e2bcf699f83a85a83340a39c22f84c6d0a2ca6a9b04fe72d4f71108b6f0c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser