CONTINUOUS INTERNET TELEMETRY24H DRIFT33,450 material changesacross 32,285 domains · 24h to ~10h ago · -4,572 vs yesterdayROTATION56 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW549 curated domains not reachablelast probe, steadySITE ERRORS33,824 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,662 sites429 rate-limit / 403 bot-block, a posture signal

yumetokyoki.com

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

This reading of yumetokyoki.com was taken 4d ago

yumetokyoki.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yumetokyoki.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 yumetokyoki.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
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:46 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 yumetokyoki.com actually stands on - every host below is a signed observation
yumetokyoki.com
A / AAAA
150.95.255.38
unattributedserves the site
NS
dns2.onamae.comdns1.onamae.com
onamae.comanswers its DNS

DNS Records

A 1

  • 150.95.255.38

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • dns2.onamae.com
  • dns1.onamae.com

SOA 1

  • dns1.onamae.com hostmaster.onamae.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject

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_87f3151768dc795c
Output Hash
8226bb0c351584808dc2acc2a083717c31777e3428e60269906cff637c5ab01e
Signature
ed25519:c52a96d2c7c45a0bd1e6d9e6464c2cef9762c47ec1dbf0acdb4950ed0cd3d4c33c1495b9169eedb362ee532aece1acfb2e007a2eae30a88ef9bd4ccbd55b3603
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser