CONTINUOUS INTERNET TELEMETRY24H DRIFT41,157 material changesacross 39,647 domains · 24h to ~7h ago · -20,919 vs yesterdayROTATION57 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,833 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,022 sites429 rate-limit / 403 bot-block, a posture signal

lacakloker.com

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

This reading of lacakloker.com was taken 12d ago

lacakloker.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lacakloker.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 lacakloker.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 09:28 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 lacakloker.com actually stands on - every host below is a signed observation
lacakloker.com
A / AAAA
172.67.163.230104.21.65.1412606:4700:3037::6815:418d2606:4700:3037::ac43:a3e6
2606serves the site
NS
leah.ns.cloudflare.compete.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
lacakloker.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.67.163.230
  • 104.21.65.141

AAAA 2

  • 2606:4700:3037::6815:418d
  • 2606:4700:3037::ac43:a3e6

NS 2

  • leah.ns.cloudflare.com
  • pete.ns.cloudflare.com

SOA 1

  • leah.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (3)

Common NameIssuerExpires
lacakloker.com C=US, O=Google Trust Services, CN=WE1 Sun, 20 Sep 2026 18:08:38 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +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_50c6a08610342a93
Output Hash
a3da43ba1e068b57f25160b4754ec804718aaeadbea02b9e890f255598bcc31c
Signature
ed25519:71799b6ad52da2b38b411f1ff2f52142f103a8237dba2e3e95ed67e5b00baf690eff0f4d1f290a5ba1c8173dba3cd305bf8fcf0fb685b5e6e729050e30389605
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser