in-spi.jp
Observed Aug 11, 2026, 04:20 UTC (17d ago). Every field below was attested with an Ed25519 signature at scan time.
in-spi.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting in-spi.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 in-spi.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.Steady. No change on record for in-spi.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.
DNS records 7
TLS certificates 2
Subdomains 0
None observed.
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
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 receiptEd25519 receiptthe raw cryptographic proof
- Receipt ID
rcpt_cce75744dc657340- Output Hash
68fa1deaa948ce2b7e87cd071e4314c4fa28a0816772237ffc79b47eb6a6e4a6- Signature
ed25519:df99fe85429ab87be84ef27e94a049a5632d600c997749809effa826cd4c0493c572b03d58e869461fb1e52c4f6b7b352adce14c47bf16b58b2b4a986f8b6100- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast