CONTINUOUS INTERNET TELEMETRY24H DRIFT55,932 material changesacross 50,731 domains · 24h to ~40m ago · -6,144 vs yesterdayROTATION51 domains moved DNS from koaladns.com to magpiedns.com, 51 moved backa rotation loop, not a migration · 24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,869 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,346 sites429 rate-limit / 403 bot-block, a posture signal

drivealert.io

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

This reading of drivealert.io was taken 4d ago

drivealert.io is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting drivealert.io 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 drivealert.io Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 05:56 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 drivealert.io actually stands on - every host below is a signed observation
drivealert.io
A / AAAA
18.216.103.8
unattributedserves the site
NS
ns-1227.awsdns-25.orgns-149.awsdns-18.comns-1941.awsdns-50.co.ukns-610.awsdns-12.net
awsdns-25.org + awsdns-18.com + moreanswers its DNS

DNS Records

A 1

  • 18.216.103.8

TXT 3

  • _f76242x4wbv6mtja2i68vmz6qd34gmt
  • _z2d2o82pp5o98vi45z9r6w6dzfwcnll
  • f76242x4wbv6mtja2i68vmz6qd34gmt

NS 4

  • ns-1227.awsdns-25.org
  • ns-149.awsdns-18.com
  • ns-1941.awsdns-50.co.uk
  • ns-610.awsdns-12.net

SOA 1

  • ns-1941.awsdns-50.co.uk awsdns-hostmaster.amazon.com

MCP_RECORDS 3

  • _f76242x4wbv6mtja2i68vmz6qd34gmt
  • _z2d2o82pp5o98vi45z9r6w6dzfwcnll
  • f76242x4wbv6mtja2i68vmz6qd34gmt

DMARC_RECORDS 3

  • _f76242x4wbv6mtja2i68vmz6qd34gmt
  • _z2d2o82pp5o98vi45z9r6w6dzfwcnll
  • f76242x4wbv6mtja2i68vmz6qd34gmt

BIMI_RECORDS 3

  • _f76242x4wbv6mtja2i68vmz6qd34gmt
  • _z2d2o82pp5o98vi45z9r6w6dzfwcnll
  • f76242x4wbv6mtja2i68vmz6qd34gmt

MTA_STS_RECORDS 3

  • _f76242x4wbv6mtja2i68vmz6qd34gmt
  • _z2d2o82pp5o98vi45z9r6w6dzfwcnll
  • f76242x4wbv6mtja2i68vmz6qd34gmt

TLS Certificates (0)

None.

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_8700f2b9b0321f00
Output Hash
08d5bb72e684a8667e05c7eb32df070ab0ea4dda76bea1645fe330fe321ece51
Signature
ed25519:e1e133e9f22d202504dc3a596fc85f3dba87d4f2b686227cfd7d8f85bc413791599d3bd6307da082d62d7bf57307badfb88883d77a217fd302a891fde29fce04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser