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, 53 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

leyserkids.jp

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

This reading of leyserkids.jp was taken 4d ago

leyserkids.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leyserkids.jp 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 leyserkids.jp 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
Runs onCloudflare
Secured byGoogle Trust Services
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 05:09 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 leyserkids.jp actually stands on - every host below is a signed observation
leyserkids.jp
A / AAAA
160.153.0.94
Cloudflareserves the site
NS
pdns07.domaincontrol.compdns08.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mailstore1.secureserver.netsmtp.secureserver.net
secureserver.netreceives its email
TLS
leyserkids.jp
Google Trust Servicesissued its certificate

DNS Records

A 1

  • 160.153.0.94

MX 2

  • 10mailstore1.secureserver.net
  • 0smtp.secureserver.net

TXT 3

  • fr65ju7171t11pq0rlrdnm863r
  • leyserkids.azurewebsites.net
  • google-site-verification=H_j63eGHTZsjoqdDyidCy8DLFU5P3SKUQKcUX0owzEE

NS 2

  • pdns07.domaincontrol.com
  • pdns08.domaincontrol.com

SOA 1

  • pdns07.domaincontrol.com dns.jomax.net

MCP_RECORDS 3

  • fr65ju7171t11pq0rlrdnm863r
  • leyserkids.azurewebsites.net
  • google-site-verification=H_j63eGHTZsjoqdDyidCy8DLFU5P3SKUQKcUX0owzEE

DMARC_RECORDS 3

  • fr65ju7171t11pq0rlrdnm863r
  • leyserkids.azurewebsites.net
  • google-site-verification=H_j63eGHTZsjoqdDyidCy8DLFU5P3SKUQKcUX0owzEE

BIMI_RECORDS 3

  • fr65ju7171t11pq0rlrdnm863r
  • leyserkids.azurewebsites.net
  • google-site-verification=H_j63eGHTZsjoqdDyidCy8DLFU5P3SKUQKcUX0owzEE

MTA_STS_RECORDS 3

  • fr65ju7171t11pq0rlrdnm863r
  • leyserkids.azurewebsites.net
  • google-site-verification=H_j63eGHTZsjoqdDyidCy8DLFU5P3SKUQKcUX0owzEE

TLS Certificates (3)

Common NameIssuerExpires
leyserkids.jp C=US, O=Google Trust Services, CN=WE1 Fri, 16 Oct 2026 14:48:08 +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_905adbfaca6f3f7b
Output Hash
28bc6bf211c0178d376150a531cbcefd4abf2a5b0f217ec83404857a27a95d7b
Signature
ed25519:1450b55f02a40a038ddbd1564570e8d509fb98b0a0c7cf3054cb3473db95781a375ca6094b93463dacbccff78b759293996dea390db5de442d30b351530d2007
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser