CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · last 24hROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 54 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,101 sites429 rate-limit / 403 bot-block, a posture signal

laubachracing.de

Observed Jul 26, 2026, 03:37 UTC (13d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of laubachracing.de was taken 13d ago

laubachracing.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting laubachracing.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 laubachracing.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-07 04:55 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 laubachracing.de actually stands on - every host below is a signed observation
laubachracing.de
A / AAAA
192.124.249.272a00:1169:103:e260::
2a00serves the site
NS
ns81.domaincontrol.comns82.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mailstore1.secureserver.netsmtp.secureserver.net
secureserver.netreceives its email

DNS Records

A 1

  • 192.124.249.27

AAAA 1

  • 2a00:1169:103:e260::

MX 2

  • 10mailstore1.secureserver.net
  • 0smtp.secureserver.net

TXT 5

  • v=spf1 include:secureserver.net ~all
  • v=DMARC1; p=reject; rua=mailto:dmarc_rua@onsecureserver.net; adkim=r; aspf=r;
  • v=spf1 include:secureserver.net ~all
  • v=spf1 include:secureserver.net ~all
  • v=spf1 include:secureserver.net ~all

NS 2

  • ns81.domaincontrol.com
  • ns82.domaincontrol.com

SOA 1

  • ns81.domaincontrol.com dns.jomax.net

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_970ae60db59eaebe
Output Hash
6df9f3bf43ed408fbb9095a68f7aef7bc4898ec823250ceb9019e8d86da9dee4
Signature
ed25519:3e2881ca894658a604a72102702720d1e72aeaba65ef40d03f415ffe6eb36827794d8cbf02df912780988fc8e0f3219edeb7d0d37e2d4e1364593d0bf5cb5007
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser