jra-ikkr.jp

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

This reading of jra-ikkr.jp was taken 15d ago

jra-ikkr.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jra-ikkr.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 jra-ikkr.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for jra-ikkr.jp in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

INFRASTRUCTURE MAPwhat jra-ikkr.jp actually stands on - every host below is a signed observation
jra-ikkr.jp
A / AAAA
190.0.2.0
unattributedserves the site
NS
01.dnsv.jp02.dnsv.jp03.dnsv.jp04.dnsv.jp
dnsv.jpanswers its DNS
MX
jra-ikkr.jp
jra-ikkr.jpreceives its email

DNS Records

A 1

  • 190.0.2.0

MX 1

  • 10jra-ikkr.jp

TXT 1

  • v=spf1 include:ica-associates.ca ip4:103.30.252.9 include:spf.mgmgsys.com ~all

NS 4

  • 01.dnsv.jp
  • 02.dnsv.jp
  • 03.dnsv.jp
  • 04.dnsv.jp

SOA 1

  • 01.dnsv.jp hostmaster.dnsv.jp

MCP_RECORDS 1

  • v=spf1 include:ica-associates.ca ip4:103.30.252.9 include:spf.mgmgsys.com ~all

DMARC_RECORDS 1

  • v=spf1 include:ica-associates.ca ip4:103.30.252.9 include:spf.mgmgsys.com ~all

BIMI_RECORDS 1

  • v=spf1 include:ica-associates.ca ip4:103.30.252.9 include:spf.mgmgsys.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:ica-associates.ca ip4:103.30.252.9 include:spf.mgmgsys.com ~all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-15 07:11 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works

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_2dcc3353e76a4281
Output Hash
09b815e43c4fdad417a3b0d323bb1fdcd3871cff84f51934ae023408db90dd61
Signature
ed25519:ee0b8ba189218d09330c6ea4153c26e8cb01e2553cc7f4ec8cac4835d1675d9742488491ae38d71c3a0d34a030cbf88d94916d2df59ddfc3d003ab705d85a401
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT36,665 material changesacross 33,278 domains · 24h to ~2h ago · -4,586 vs yesterdayROTATION79 domains moved DNS from magpiedns.com to kirklanddc.com, 74 moved backa rotation loop, not a migration · 24hEMAIL DRIFT6 domains switched email provider24hNOW489 curated domains not reachablelast probe, steadySITE ERRORS33,768 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,234 sites429 rate-limit / 403 bot-block, a posture signal