CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~2h 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 ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,518 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,266 sites429 rate-limit / 403 bot-block, a posture signal

reitzner.de

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

This reading of reitzner.de was taken 5d ago

reitzner.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting reitzner.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 reitzner.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Email byBrevo (Sendinblue)
Secured byLet's Encrypt
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 00:14 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 reitzner.de actually stands on - every host below is a signed observation
reitzner.de
A / AAAA
85.13.168.87
unattributedserves the site
NS
drew.ns.cloudflare.commia.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mx01.hornetsecurity.commx02.hornetsecurity.commx03.hornetsecurity.commx04.hornetsecurity.com
Brevo (Sendinblue)receives its email
TLS
reitzner.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 85.13.168.87

MX 4

  • 10mx01.hornetsecurity.com
  • 20mx02.hornetsecurity.com
  • 30mx03.hornetsecurity.com
  • 40mx04.hornetsecurity.com

TXT 7

  • MS=7CC9AB68CBC32FE4B49C0688E57DC6329D6F9F5B
  • a9sm9ttugdetd9ftlb0kjpt7m0
  • brevo-code:c3ef69e8de506b14d8bc4c84718480c1
  • globalsign-domain-verification=B7PoYwHT1Pe61y7MfEONJLDy8PbiR44jBR6I4Oj-rc
  • m3ycCEY5L+FwsT90kgXDGjZPtPrzCVHoH3TRFk+sdYURcZBapzn9lyar5PIsPr4fo+mrzvKi7fJ9FNrNFfcHUA==
  • v=spf1 include:spf.hornetsecurity.com include:ispgateway.de include:spf.sendinblue.com include:spf.protection.outlook.com mx ~all
  • zone-ownership-verification-b8bdc712a07285e66e1a93d7de2664d672f5312aa14b8b76c4df29d825b2b114

NS 2

  • drew.ns.cloudflare.com
  • mia.ns.cloudflare.com

SOA 1

  • drew.ns.cloudflare.com dns.cloudflare.com

SRV 1

  • autodiscover.outlook.com:443 p0

CAA 20

  • issue "cloudflare.com"
  • issue "comodoca.com"
  • issue "digicert.com; cansignhttpexchanges=yes"
  • issue "letsencrypt.com"
  • issue "letsencrypt.org"
  • issue "pki.goog; cansignhttpexchanges=yes"
  • issue "sectigo.com"
  • issue "ssl.com"
  • issue "starfield.com"
  • issue "starfieldtech.com"

MCP_RECORDS 2

  • globalsign-domain-verification=B7PoYwHT1Pe61y7MfEONJLDy8PbiR44jBR6I4Oj-rc
  • v=spf1 include:spf.hornetsecurity.com include:spf.protection.outlook.com ~all

DMARC_RECORDS 1

  • v=DMARC1;p=quarantine;pct=100

BIMI_RECORDS 2

  • globalsign-domain-verification=B7PoYwHT1Pe61y7MfEONJLDy8PbiR44jBR6I4Oj-rc
  • v=spf1 include:spf.hornetsecurity.com include:spf.protection.outlook.com ~all

MTA_STS_RECORDS 2

  • globalsign-domain-verification=B7PoYwHT1Pe61y7MfEONJLDy8PbiR44jBR6I4Oj-rc
  • v=spf1 include:spf.hornetsecurity.com include:spf.protection.outlook.com ~all

TLS Certificates (4)

Common NameIssuerExpires
reitzner.de C=US, O=Let's Encrypt, CN=YE2 Sat, 24 Oct 2026 01:15:05 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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