CONTINUOUS INTERNET TELEMETRY24H DRIFT53,215 material changesacross 49,422 domains · 24h to ~2h ago · -8,861 vs yesterdayROTATION49 domains moved DNS from kirklanddc.com to koaladns.com, 48 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,874 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,203 sites429 rate-limit / 403 bot-block, a posture signal

anclafs.com

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

This reading of anclafs.com was taken 4d ago

anclafs.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting anclafs.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 anclafs.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onTrellian Pty. Limited
Secured byLet's Encrypt
Registered withDynadot Inc
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 07:00 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 anclafs.com actually stands on - every host below is a signed observation
anclafs.com
A / AAAA
103.224.182.253
Trellian Pty. Limitedserves the site
NS
ns2.abovedomains.comns1.abovedomains.com
abovedomains.comanswers its DNS
MX
alltheemails.com
alltheemails.comreceives its email
TLS
anclafs.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10alltheemails.com

TXT 1

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

NS 2

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

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

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

DMARC_RECORDS 1

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

BIMI_RECORDS 1

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

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -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_3e6468ad39fb292f
Output Hash
67064fffb6f368b798467eec6b8fca70571688c3e078142f80014eab8e68b160
Signature
ed25519:8301cbeba2037c10c92bab0054eeecd0f93b96ef22ca0cd79c6c7b627f22820914872fb8f7955ebe7ee6fe23eed88bce04f99d613d5b7578c966b4ff912b3e0a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser