CONTINUOUS INTERNET TELEMETRY24H DRIFT21,097 material changesacross 19,583 domains · 24h to ~3h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,520 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,157 sites429 rate-limit / 403 bot-block, a posture signal

lagazettedeberlin.de

Observed Jul 27, 2026, 05:08 UTC (12d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of lagazettedeberlin.de was taken 12d ago

lagazettedeberlin.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lagazettedeberlin.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 lagazettedeberlin.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 16:54 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 lagazettedeberlin.de actually stands on - every host below is a signed observation
lagazettedeberlin.de
A / AAAA
103.224.182.245
unattributedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
lovebugscrapbooking.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.245

MX 1

  • 10park-mx.above.com

TXT 5

  • v=spf1 ip6:fdcf:abda:4154::/48 -all
  • v=spf1 ip6:fdcf:abda:4154::/48 -all
  • v=spf1 ip6:fdcf:abda:4154::/48 -all
  • v=spf1 ip6:fdcf:abda:4154::/48 -all
  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns1.abovedomains.com
  • ns2.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

TLS Certificates (3)

Common NameIssuerExpires
lovebugscrapbooking.com C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 07:01:44 +0000
YR2 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 (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_1f23add86f19fe94
Output Hash
b83fe86a1fed782da4bffd73bf88c63fdfbc465d00274b86e392bba12c40d422
Signature
ed25519:cda14b11b01a89f994f249582a1849591fbf6f7bfda272eead5babdd21a183063989dee191b9ff343af6508fd8ffbfa04eb27f7e86da42c6eaef1d6af9d4e707
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser