CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

usgamuseum.com

Observed Jul 27, 2026, 15:49 UTC (9d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of usgamuseum.com was taken 9d ago

usgamuseum.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting usgamuseum.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 usgamuseum.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
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-04 08:13 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 usgamuseum.com actually stands on - every host below is a signed observation
usgamuseum.com
A / AAAA
104.77.178.167
unattributedserves the site
NS
ns1.markmonitor.comns3.markmonitor.com
markmonitor.comanswers its DNS
TLS
sonarqube.usga.org
Let's Encryptissued its certificate

DNS Records

A 1

  • 104.77.178.167

MX 1

  • 0

TXT 8

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

NS 2

  • ns1.markmonitor.com
  • ns3.markmonitor.com

SOA 1

  • ns1.markmonitor.com hostmaster.markmonitor.com

TLS Certificates (3)

Common NameIssuerExpires
sonarqube.usga.org C=US, O=Let's Encrypt, CN=YR1 Wed, 14 Oct 2026 14:01:56 +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 (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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_3af374cc189a2e1f
Output Hash
61c783149478a0c658890fb7e4adeb0cd9b77776f8d6cd03f8d485c4da606483
Signature
ed25519:6ed9c2f2bc8211171ec4867d6f16e2dea9a5856741cf3c54364ab179f380cdee65e68de66ba08f768e1187d41061b77e3000382e9be10501168931097e7bc10c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser