CONTINUOUS INTERNET TELEMETRY24H DRIFT71,617 material changesacross 67,026 domains · 24h to ~35m ago · +37,000 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW533 curated domains not reachablelast probe, steadySITE ERRORS33,847 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 126,417 sites429 rate-limit / 403 bot-block, a posture signal

anderes-berlin.de

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

This reading of anderes-berlin.de was taken 3d ago

anderes-berlin.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting anderes-berlin.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 anderes-berlin.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 byGoogle (SPF sender)
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 11:09 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 anderes-berlin.de actually stands on - every host below is a signed observation
anderes-berlin.de
A / AAAA
85.214.54.99
unattributedserves the site
NS
ns3.stratoserver.netns4.stratoserver.net
stratoserver.netanswers its DNS
MX
mail.anderes-berlin.de
Google (SPF sender)receives its email
TLS
anderes-berlin.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 85.214.54.99

MX 1

  • 10mail.anderes-berlin.de

TXT 1

  • v=spf1 include:_spf.google.com ~all

NS 2

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

SOA 1

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

MCP_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

BIMI_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.google.com ~all

TLS Certificates (3)

Common NameIssuerExpires
anderes-berlin.de C=US, O=Let's Encrypt, CN=YR1 Sun, 18 Oct 2026 21:52:09 +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 (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_2f51e36caf928d29
Output Hash
f5aacc3ef2c9243379843808d4d4f73d3e7beef3488f56d04683f99604e84757
Signature
ed25519:5af7e85ce17ffc4441e97f9022f55ea43b14a9d76f61c0ac02be7a989fa545e4af923ec3e3c5be31388a06ec55a2e17ccecc33e4c8dddb178f18c654b957d006
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser