CONTINUOUS INTERNET TELEMETRY24H DRIFT50,294 material changesacross 44,212 domains · 24h to ~60m ago · +15,888 vs yesterdayROTATION59 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW612 curated domains not reachablelast probe, steadySITE ERRORS34,081 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,120 sites429 rate-limit / 403 bot-block, a posture signal

randomterrain.com

Observed Jul 26, 2026, 11:03 UTC (14d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of randomterrain.com was taken 14d ago

randomterrain.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting randomterrain.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 randomterrain.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
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-09 03:26 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 randomterrain.com actually stands on - every host below is a signed observation
randomterrain.com
A / AAAA
20.83.153.186
unattributedserves the site
NS
ns2.turbify.comns1.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.netmx-biz.mail.am0.yahoodns.net
yahoodns.netreceives its email
TLS
www.randomterrain.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 20.83.153.186

MX 2

  • 30mx-biz.mail.am0.yahoodns.net
  • 20mx-biz.mail.am0.yahoodns.net

TXT 4

  • v=spf1 a mx ip4:20.83.153.186 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.83.153.186 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.83.153.186 include:relay.mailchannels.net -all
  • v=spf1 a mx ip4:20.83.153.186 include:relay.mailchannels.net -all

NS 2

  • ns2.turbify.com
  • ns1.turbify.com

SOA 1

  • ns1.turbify.com hostmaster.randomterrain.com

TLS Certificates (3)

Common NameIssuerExpires
www.randomterrain.com C=US, O=Let's Encrypt, CN=YR1 Mon, 31 Aug 2026 11:46:11 +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_bb5b9fa2e0474b6f
Output Hash
e25aebb90604f1df168a7f570921f6a0af0d40d793dea04c177a03c2fdd71c84
Signature
ed25519:50a3f8f28bd461f5d7ae20aaa0c011c61632d10d2d302baad611e755d76160ba3b47f9409a06efad8bb0441dcbb694328c300f0a171452bc757e2501cab47f08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser