CONTINUOUS INTERNET TELEMETRY24H DRIFT49,366 material changesacross 43,517 domains · 24h to ~80m ago · +14,960 vs yesterdayROTATION54 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW618 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,884 sites429 rate-limit / 403 bot-block, a posture signal

eatndo.com

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

This reading of eatndo.com was taken 14d ago

eatndo.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting eatndo.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 eatndo.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 06:05 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 eatndo.com actually stands on - every host below is a signed observation
eatndo.com
A / AAAA
103.224.182.246
unattributedserves the site
NS
ns2.abovedomains.comns1.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
bhd4.xyz
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.246

MX 1

  • 10park-mx.above.com

TXT 5

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

NS 2

  • ns2.abovedomains.com
  • ns1.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

TLS Certificates (3)

Common NameIssuerExpires
bhd4.xyz C=US, O=Let's Encrypt, CN=YR2 Tue, 13 Oct 2026 11:03:10 +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 (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_950de20988e0ace6
Output Hash
dd9b0e75f04dc8afffe293a2632a4fbbd0d8bd916b853d2fc1471d52b66e3ff6
Signature
ed25519:245727739ecd7a1827e67ae117f81bd4d12cec69fa7c41eb33f12b328cafbf2512b5ad530a56192dfdb5e601ef03d2d717e816cf8bee39c2abf13c2d4fec4402
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser