CONTINUOUS INTERNET TELEMETRY24H DRIFT54,366 material changesacross 47,273 domains · 24h to ~40m ago · +19,960 vs yesterdayROTATION54 domains moved DNS from magpiedns.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hNOW610 curated domains not reachablelast probe, steadySITE ERRORS34,087 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,405 sites429 rate-limit / 403 bot-block, a posture signal

easybook-project.org

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

This reading of easybook-project.org was taken 14d ago

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

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10alltheemails.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

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

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

TLS Certificates (3)

Common NameIssuerExpires
matcocarscan.com C=US, O=Let's Encrypt, CN=YR2 Sun, 04 Oct 2026 23:44:59 +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_54c200c9af7a1b56
Output Hash
6693bc98835474125cf9859e062f5192548d3bb176f90c692bc14553c15f927c
Signature
ed25519:bb0d06c216e0307045e544e37625208d2bfc76e3ddf61bd1d85ec292721f0758addd3652a4e62d94a925a33e423caf15bc03c304f5a99610250092511bef9b0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser