CONTINUOUS INTERNET TELEMETRY24H DRIFT43,836 material changesacross 42,208 domains · 24h to ~6h ago · -18,240 vs yesterdayROTATION55 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,888 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,377 sites429 rate-limit / 403 bot-block, a posture signal

lindows.com

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

This reading of lindows.com was taken 3d ago

lindows.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lindows.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 lindows.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 02:47 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 lindows.com actually stands on - every host below is a signed observation
lindows.com
A / AAAA
72.251.7.2272.251.7.23
unattributedserves the site
NS
ns1.lander.d.parity.domainsns2.lander.d.parity.domains
parity.domainsanswers its DNS
TLS
lindows.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 72.251.7.22
  • 72.251.7.23

NS 2

  • ns1.lander.d.parity.domains
  • ns2.lander.d.parity.domains

SOA 1

  • ns1.lander.d.parity.domains hostmaster.lander.d.parity.domains

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_1afe6509586a65b9
Output Hash
411ba869e1144a96b6df394c80634045ac54c327a6b65f32f5a23c2d201a0530
Signature
ed25519:efdc9f7392b849ba92b46930ee5eae0fbf10fe8f3f28bed5dd245bfab0b4fa6b61f473a2b12ff300f64401a00d197ec54a7311f1538ef7849783bca7f6b8fc0a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser