CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · 24h to ~30m agoSHIFT21 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,263 sites429 rate-limit / 403 bot-block, a posture signal

uswmidam.org

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

This reading of uswmidam.org was taken 1d ago

uswmidam.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting uswmidam.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 uswmidam.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Guarded by a firewall
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 19:53 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 uswmidam.org actually stands on - every host below is a signed observation
uswmidam.org
A / AAAA
23.212.249.21423.212.249.219
unattributedserves the site
NS
a1-63.akam.neta28-65.akam.neta13-67.akam.neta4-66.akam.net+2 more
akam.netanswers its DNS
TLS
playerprofile.usga.org
Let's Encryptissued its certificate

DNS Records

A 2

  • 23.212.249.214
  • 23.212.249.219

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 6

  • a1-63.akam.net
  • a28-65.akam.net
  • a13-67.akam.net
  • a4-66.akam.net
  • a2-64.akam.net
  • a11-66.akam.net

SOA 1

  • a4-66.akam.net hostmaster.akamai.com

MCP_RECORDS 1

  • v=DKIM1; p=v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject

BIMI_RECORDS 1

  • v=DKIM1; p=v=spf1 -all

MTA_STS_RECORDS 1

  • v=DKIM1; p=v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
playerprofile.usga.org C=US, O=Let's Encrypt, CN=YR2 Tue, 27 Oct 2026 13:56:01 +0000
YR2 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 (1)

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_e4139d9c6396a064
Output Hash
86f9d2c510f142396393249702dbad06bc074402fb549228ef11db79bdbf7e20
Signature
ed25519:aac7ad6a918afb6f9f0b80c005b389f9ddbc7d8285a015df4b238071d0c534945ed4dbea505a4a82f17eeb859a29896fea61d6ff95031bb2b70c7600b2ce430f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser