CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedROTATION48 domains moved DNS from koaladns.com to kirklanddc.com, 46 moved backa rotation loop, not a migration · 24hNOW592 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,513 sites429 rate-limit / 403 bot-block, a posture signal

lehrerforen.de

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

This reading of lehrerforen.de was taken 5d ago

lehrerforen.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lehrerforen.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 lehrerforen.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
Secured byLet's Encrypt
3 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 15:21 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 lehrerforen.de actually stands on - every host below is a signed observation
lehrerforen.de
A / AAAA
85.214.35.8
unattributedserves the site
NS
ns4.stratoserver.netns3.stratoserver.net
stratoserver.netanswers its DNS
MX
lehrerforen.de
lehrerforen.dereceives its email
TLS
lehrerforen.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 85.214.35.8

MX 1

  • 10lehrerforen.de

TXT 1

  • v=spf1 mx -all

NS 2

  • ns4.stratoserver.net
  • ns3.stratoserver.net

SOA 1

  • ns3.stratoserver.net hostmaster.strato-rz.de

MCP_RECORDS 1

  • v=spf1 mx -all

DMARC_RECORDS 1

  • v=spf1 mx -all

BIMI_RECORDS 1

  • v=spf1 mx -all

MTA_STS_RECORDS 1

  • v=spf1 mx -all

TLS Certificates (3)

Common NameIssuerExpires
lehrerforen.de C=US, O=Let's Encrypt, CN=YR1 Sun, 13 Sep 2026 00:05:54 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (3)

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_a09acbc8c4a72d7d
Output Hash
67e4452b02e725ebbaa00c17515d4c6f9277092a69de26afe7e008d462e75953
Signature
ed25519:5e273d0d852f5973a654c23ee82ac2104a528603ab6a5df2b828a0028d73b5008d5a92447751e1c02388c5217cf0d5f751eb634631a2b439ed390237679ec904
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser