CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · 24h to ~40m agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,530 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,011 sites429 rate-limit / 403 bot-block, a posture signal

dripstat.com

Observed Aug 3, 2026, 00:58 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of dripstat.com was taken 5d ago

dripstat.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dripstat.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 dripstat.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byLet's Encrypt
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 05:59 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 dripstat.com actually stands on - every host below is a signed observation
dripstat.com
A / AAAA
172.67.214.69104.21.78.72606:4700:3037::ac43:d6452606:4700:3036::6815:4e07
2606serves the site
NS
eleanor.ns.cloudflare.comeverton.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
dripstat.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.67.214.69
  • 104.21.78.7

AAAA 2

  • 2606:4700:3037::ac43:d645
  • 2606:4700:3036::6815:4e07

NS 2

  • eleanor.ns.cloudflare.com
  • everton.ns.cloudflare.com

SOA 1

  • eleanor.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (3)

Common NameIssuerExpires
dripstat.com C=US, O=Google Trust Services, CN=WE1 Fri, 30 Oct 2026 09:48:10 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +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_348744bd250482ba
Output Hash
fb75ec0bbc7eba5a65b203d94c1994d284d39c59c53eb1ff1bbadef123dfd118
Signature
ed25519:0a0a8c5fa23704ec72a33913dc96e1044df6590c25da3616e315669977b69ecaccb2f11fdd79b694ad4e625b52ce5936578af54f91fabe98afddbbe3a8de1103
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser