CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~3h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

docomo-live.jp

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

This reading of docomo-live.jp was taken 3d ago

docomo-live.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting docomo-live.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 docomo-live.jp 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-05 09:21 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 docomo-live.jp actually stands on - every host below is a signed observation
docomo-live.jp
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_c76a2000f8b931ba
Output Hash
a92233e2e3c119ebb0add89bf38b2788911ab691488ee2f33aac0a96a2a7dc58
Signature
ed25519:6007c9550f6826edcbdce2c83d062debc771d4166dd8ee8e7335b76b6511c8c907990a8a8878d7f24df91752f09e2ee7f4164479f381b6270730df234e4f400d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser