CONTINUOUS INTERNET TELEMETRY24H DRIFT49,307 material changesacross 44,221 domains · 24h to ~2h ago · +14,901 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 55 moved backa rotation loop, not a migration · 24hNOW607 curated domains not reachablelast probe, steadySITE ERRORS34,084 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,310 sites429 rate-limit / 403 bot-block, a posture signal

roaddanger.org

Observed Aug 2, 2026, 20:37 UTC (7d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of roaddanger.org was taken 7d ago

roaddanger.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting roaddanger.org 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 roaddanger.org 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
IPv6 · 15 subdomains · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 13:52 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 roaddanger.org actually stands on - every host below is a signed observation
roaddanger.org
A / AAAA
116.203.143.952a01:4f8:c2c:8aba::1
2a01serves the site
NS
ns0.transip.netns1.transip.nlns2.transip.eu
transip.net + transip.nl + moreanswers its DNS
TLS
roaddanger.org
Let's Encryptissued its certificate

DNS Records

A 1

  • 116.203.143.95

AAAA 1

  • 2a01:4f8:c2c:8aba::1

TXT 1

  • v=spf1 a mx ~all

NS 3

  • ns0.transip.net
  • ns1.transip.nl
  • ns2.transip.eu

SOA 1

  • ns0.transip.net hostmaster.transip.nl

MCP_RECORDS 1

  • v=spf1 a mx ~all

DMARC_RECORDS 1

  • v=spf1 a mx ~all

BIMI_RECORDS 1

  • v=spf1 a mx ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx ~all

TLS Certificates (3)

Common NameIssuerExpires
roaddanger.org C=US, O=Let's Encrypt, CN=YR1 Mon, 07 Sep 2026 06:49:17 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (15)

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_e4e749955d322018
Output Hash
40e250c90a4a2c5c638295ec09fb3748f3a4cb2bd247634152e93e7d4b9c23f7
Signature
ed25519:a4c6d6b01dd17691533fa3cd219e9e1f3113faafb4c06094aaa983f95f0c594ce16aff2bcfac53dd16b4fc92869ac845450aea63d10bcafd13a828c18450ea02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser