CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedDNS DRIFT78 domains changed DNS providertop destination koaladns.comNOW592 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

lindadesign.de

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

This reading of lindadesign.de was taken 11d ago

lindadesign.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lindadesign.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 lindadesign.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 21:07 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 lindadesign.de actually stands on - every host below is a signed observation
lindadesign.de
A / AAAA
91.195.241.232
unattributedserves the site
NS
sl1.sedo.comsl2.sedo.com
sedo.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
lindadesign.de
DigiCert Incissued its certificate

DNS Records

A 1

  • 91.195.241.232

MX 1

  • 0localhost

TXT 5

  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • sl1.sedo.com
  • sl2.sedo.com

SOA 1

  • sl1.sedo.com hostmaster.sedo.de

TLS Certificates (2)

Common NameIssuerExpires
lindadesign.de C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G2 Thu, 13 Aug 2026 23:59:59 +0000
Encryption Everywhere DV TLS CA - G2 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Sat, 27 Nov 2027 12:46:40 +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_b3c23ac777666d18
Output Hash
1d5c9cc9bf8b780e18e8a72dffc7771fb3f18bbaa0a5ce5d63291833f59a0c43
Signature
ed25519:d32bc1e891c6279c2cecac9849561f7fc90cf2228e53571e5246f696ff5770548acaa6903e80d64320a1b3b914583f5cee0acae5660bd7d62411d50af1b49a01
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser