CONTINUOUS INTERNET TELEMETRY24H DRIFT43,686 material changesacross 39,414 domains · 24h to ~25m ago · +9,069 vs yesterdaySHIFT35 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW541 curated domains not reachablelast probe, steadySITE ERRORS33,780 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 153,652 sites429 rate-limit / 403 bot-block, a posture signal

earthythailand.com

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

This reading of earthythailand.com was taken 2d ago

earthythailand.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting earthythailand.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 earthythailand.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 14:07 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 earthythailand.com actually stands on - every host below is a signed observation
earthythailand.com
A / AAAA
103.224.182.251
unattributedserves the site
NS
ns3.abovedomains.comns4.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
companyofheroesgame.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.251

MX 1

  • 10park-mx.above.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns3.abovedomains.com
  • ns4.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
companyofheroesgame.com C=US, O=Let's Encrypt, CN=YR1 Tue, 06 Oct 2026 06:28:39 +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 (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_bfce619c280ea6f8
Output Hash
10f163532494425c273e19edaa2b5ed40b82544990b88882c27a082cca842a51
Signature
ed25519:5a9ee866ed4a8b72477216f7b47e47e75b75469f6a1e8d9b0a127cb171c9a6536e6149c31b160f7f8506f7c01dedbfc2abddcc03dcde4bc65be0a9a89b505f0c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser