CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~60m ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,178 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,838 sites429 rate-limit / 403 bot-block, a posture signal

animea.net

Observed Aug 3, 2026, 00:08 UTC (7d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of animea.net was taken 7d ago

animea.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting animea.net 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 animea.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onOVH SAS
Email byGoogle Workspace
Registered withNameCheap, Inc.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 18:09 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 animea.net actually stands on - every host below is a signed observation
animea.net
A / AAAA
192.99.32.5
OVH SASserves the site
NS
aria.ns.cloudflare.comseth.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
aspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email

DNS Records

A 1

  • 192.99.32.5

MX 5

  • 1aspmx.l.google.com
  • 10aspmx2.googlemail.com
  • 10aspmx3.googlemail.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 1

  • v=spf1ip4:67.220.212.82amx~all

NS 2

  • aria.ns.cloudflare.com
  • seth.ns.cloudflare.com

SOA 1

  • aria.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1ip4:67.220.212.82amx~all

DMARC_RECORDS 1

  • v=spf1ip4:67.220.212.82amx~all

BIMI_RECORDS 1

  • v=spf1ip4:67.220.212.82amx~all

MTA_STS_RECORDS 1

  • v=spf1ip4:67.220.212.82amx~all

TLS Certificates (0)

None.

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_de635a599d75ad66
Output Hash
20b4a6109910b7b86f54868c5fd076326b2a8a15d2b4f4f9ca2515d16202ecbc
Signature
ed25519:d6465745aa90ce933f0e2b3e03cdd6023a5b339db1ea428d2f9c82b97c8a53c870f946305452bd47bad57ac31b2935372065f978d66aecac48d9053da030e200
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser