CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~3h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,520 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,157 sites429 rate-limit / 403 bot-block, a posture signal

leobach.de

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

This reading of leobach.de was taken 6d ago

leobach.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leobach.de 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 leobach.de 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.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-08 06:17 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 leobach.de actually stands on - every host below is a signed observation
leobach.de
A / AAAA
127.0.0.1
unattributedserves the site
NS
ns3.dyndnsfree.dens2.dyndnsfree.dens1.dyndnsfree.de
dyndnsfree.deanswers its DNS
MX
leobach.de
leobach.dereceives its email

DNS Records

A 1

  • 127.0.0.1

MX 1

  • 10leobach.de

TXT 1

  • v=spf1 include:dynup.de -all

NS 3

  • ns3.dyndnsfree.de
  • ns2.dyndnsfree.de
  • ns1.dyndnsfree.de

SOA 1

  • ns1.dyndnsfree.de ns2.dyndnsfree.de

MCP_RECORDS 1

  • v=spf1 include:dynup.de -all

DMARC_RECORDS 1

  • v=spf1 include:dynup.de -all

BIMI_RECORDS 1

  • v=spf1 include:dynup.de -all

MTA_STS_RECORDS 1

  • v=spf1 include:dynup.de -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_6bd48e1cc489a6dd
Output Hash
69ef89c40c5dbfa392a8e13975cd48483f31150ea9334399181c325ee80f5a2d
Signature
ed25519:8f447da752673ad5c80150c7f6988b676dbc33d10327f27b77df5860a43cd0fc529edce6093d0c1f05b25bfb4e3927f07391152a14c5ba2138843df29d264501
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser