CONTINUOUS INTERNET TELEMETRY24H DRIFT29,105 material changesacross 28,144 domains · 24h to ~13h ago · -8,917 vs yesterdayROTATION59 domains moved DNS from kirklanddc.com to koaladns.com, 55 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW560 curated domains not reachable+29 vs yesterdaySITE ERRORS33,740 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,660 sites429 rate-limit / 403 bot-block, a posture signal

langenberg.com

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

This reading of langenberg.com was taken 4d ago

langenberg.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting langenberg.com 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 langenberg.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byZeroSSL GmbH
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 23:53 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 langenberg.com actually stands on - every host below is a signed observation
langenberg.com
A / AAAA
208.91.196.105
unattributedserves the site
NS
sk.s5.cm.ns2.39.ztomy.comsk.s5.cm.ns1.39.ztomy.com
ztomy.comanswers its DNS
MX
\~
unattributedreceives its email
TLS
langenberg.com
ZeroSSL GmbHissued its certificate

DNS Records

A 1

  • 208.91.196.105

MX 1

  • 300\~

TXT 1

  • v=spf1 a -all

NS 2

  • sk.s5.cm.ns2.39.ztomy.com
  • sk.s5.cm.ns1.39.ztomy.com

SOA 1

  • sk.s5.cm.ns1.39.ztomy.com abuse.confluence-networks.com

MCP_RECORDS 1

  • v=spf1 a -all

DMARC_RECORDS 1

  • v=spf1 a -all

BIMI_RECORDS 1

  • v=spf1 a -all

MTA_STS_RECORDS 1

  • v=spf1 a -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_0b3f0fe669817bbe
Output Hash
8388fba5a354129ab93a50f43780bb4430c746d446359f9614de0ed0ad5d641c
Signature
ed25519:ec42e45f7dad2c54bb3f455bc1820c1264f50410a9e7953a4a5cb0f4c6cb3036e59a16ca1359abbd6364a958d55bf445b984be1a8bbfce27cd3f62d01af0a006
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser