CONTINUOUS INTERNET TELEMETRY24H DRIFT29,105 material changesacross 28,144 domains · 24h to ~13h ago · -8,917 vs yesterdayROTATION58 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

laurinka.com

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

This reading of laurinka.com was taken 12d ago

laurinka.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting laurinka.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 laurinka.com 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
Email byGoogle Workspace
Also usesGoogle Search Console
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 04:11 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 laurinka.com actually stands on - every host below is a signed observation
laurinka.com
A / AAAA
91.151.18.22
unattributedserves the site
NS
cns2.cloudpit.comcns1.cloudpit.decns3.cloudpit.io
cloudpit.com + cloudpit.de + moreanswers its DNS
MX
aspmx2.googlemail.comaspmx3.googlemail.comalt1.aspmx.l.google.comalt2.aspmx.l.google.com+1 more
Google Workspacereceives its email

DNS Records

A 1

  • 91.151.18.22

MX 5

  • 10aspmx2.googlemail.com
  • 10aspmx3.googlemail.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com
  • 1aspmx.l.google.com

TXT 5

  • google-site-verification=FUrggOVno3sUZ1C5JD8avAWE7VzawthnYt5TwAKXKMI
  • google-site-verification=FUrggOVno3sUZ1C5JD8avAWE7VzawthnYt5TwAKXKMI
  • google-site-verification=FUrggOVno3sUZ1C5JD8avAWE7VzawthnYt5TwAKXKMI
  • google-site-verification=FUrggOVno3sUZ1C5JD8avAWE7VzawthnYt5TwAKXKMI
  • google-site-verification=FUrggOVno3sUZ1C5JD8avAWE7VzawthnYt5TwAKXKMI

NS 3

  • cns2.cloudpit.com
  • cns1.cloudpit.de
  • cns3.cloudpit.io

SOA 1

  • cns1.cloudpit.de hostmaster.dogado.de

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_e8bdeb42f22e97ad
Output Hash
59b1afbb27ed00cd3c5233f494e2b49cdfb38d37e75a6717a6ffac078216af64
Signature
ed25519:074ff7898ae2be63fb6845a7764f94ff6fb42f139e75122ea76c40e8eddb281d11318dec259c24eb46fb856a4d5e58825710c62c43d354d7cbd87f11730c8605
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser