CONTINUOUS INTERNET TELEMETRY24H DRIFT48,244 material changesacross 46,548 domains · 24h to ~5h ago · +13,627 vs yesterdaySHIFT101 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW534 curated domains not reachablelast probe, steadySITE ERRORS33,821 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 135,269 sites429 rate-limit / 403 bot-block, a posture signal

visitjapan.jp

Observed Jul 26, 2026, 09:09 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of visitjapan.jp was taken 10d ago

visitjapan.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting visitjapan.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 visitjapan.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.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 01:44 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 visitjapan.jp actually stands on - every host below is a signed observation
visitjapan.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 5

  • v=spf1 -all
  • v=DMARC1; p=reject
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

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

SOA 1

  • dns1.onamae.com hostmaster.onamae.com

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_25c4781356f7fa17
Output Hash
07fe4c322336c72a3ea019be3cbb07d2001cfe04dd10b43a78c2f178e43de7c2
Signature
ed25519:395f8194772a9f859bef2ed4b65070e776c3e3f9a4a1f8ab4153d393b9c09957b550be6e028022733e3473b19c32dab93f1f2994f52421a1903c40652994e80b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser