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

linux-kernel-labs-zh.xyz

Observed Aug 2, 2026, 22:37 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of linux-kernel-labs-zh.xyz was taken 4d ago

linux-kernel-labs-zh.xyz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting linux-kernel-labs-zh.xyz 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 linux-kernel-labs-zh.xyz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-06 06:49 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 linux-kernel-labs-zh.xyz actually stands on - every host below is a signed observation
linux-kernel-labs-zh.xyz
A / AAAA
172.237.146.18172.237.146.46172.237.146.39
unattributedserves the site
NS
ns2.parklogic.comns1.parklogic.com
parklogic.comanswers its DNS
MX
mx156.hostedmxserver.com
hostedmxserver.comreceives its email

DNS Records

A 3

  • 172.237.146.18
  • 172.237.146.46
  • 172.237.146.39

MX 1

  • 390mx156.hostedmxserver.com

TXT 1

  • v=spf1 -all

NS 2

  • ns2.parklogic.com
  • ns1.parklogic.com

SOA 1

  • ns1.parklogic.com hostmaster.linux-kernel-labs-zh.xyz

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

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_2cf637192d310e0a
Output Hash
62657e81feb1bc3db27eff5d81e41a2363183f062060c5b25341572355f60f5e
Signature
ed25519:a5af5179c1bed74b05fd3b03af658e0d80091a1d363523bfe3a65c4dc549064d7217d52a88a03bd78b16d54a649a5a5e0d13cac75f5a1f83da37b4ed14ad640d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser