CONTINUOUS INTERNET TELEMETRY24H DRIFT30,429 material changesacross 29,264 domains · 24h to ~3h agoSHIFT26 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW564 curated domains not reachablelast probe, steadySITE ERRORS34,078 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,336 sites429 rate-limit / 403 bot-block, a posture signal

zeileis.org

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

This reading of zeileis.org was taken 1d ago

zeileis.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zeileis.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 zeileis.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 20:41 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 zeileis.org actually stands on - every host below is a signed observation
zeileis.org
A / AAAA
138.232.16.219fe80::21a:4aff:fe31:10db
fe80serves the site
NS
ns-129-a.gandi.netns-23-b.gandi.netns-193-c.gandi.net
gandi.netanswers its DNS
MX
mxext3.mailbox.orgmxext1.mailbox.orgmxext2.mailbox.org
mailbox.orgreceives its email

DNS Records

A 1

  • 138.232.16.219

AAAA 1

  • fe80::21a:4aff:fe31:10db

MX 3

  • 20mxext3.mailbox.org
  • 10mxext1.mailbox.org
  • 10mxext2.mailbox.org

TXT 1

  • v=spf1 include:mailbox.org ~all

NS 3

  • ns-129-a.gandi.net
  • ns-23-b.gandi.net
  • ns-193-c.gandi.net

SOA 1

  • ns1.gandi.net hostmaster.gandi.net

MCP_RECORDS 1

  • v=spf1 include:mailbox.org ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;rua=mailto:postmaster@zeileis.org

BIMI_RECORDS 1

  • v=spf1 include:mailbox.org ~all

MTA_STS_RECORDS 1

  • v=spf1 include:mailbox.org ~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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_33cafcc24bb20a53
Output Hash
d0549f142db99d8188ca8da71ec6d9c8ef64365ab6ddb464d8bdfc964237d099
Signature
ed25519:9279ef8e6d53ce2d69c3c219fbb864e72415a81a36d5e9e39e1e0bdd60035208de6f1a41e1c69b920fc4e6146fce7b46fbc7bd19f911df4c550444078fcd0000
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser