nagoyaaqua.jp
Observed Jul 20, 2026, 21:27 UTC (42d ago). Every field below was attested with an Ed25519 signature at scan time.
nagoyaaqua.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting nagoyaaqua.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 nagoyaaqua.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.Steady. No change on record for nagoyaaqua.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.
HTTPS probe
Nothing answered on 443 inside our budget: 2 attempts of 3s each, from Cloudflare's network. DNS resolved, so the name and its delegation are fine - the failure is below that, at the connection or HTTP layer.
It does NOT mean the site is down for everyone. Our budget is deliberately tight so a two-million-domain sweep stays affordable, and a site that is merely slow will miss it while working fine in a browser.
Probed from Cloudflare's network. A site can be healthy and still not answer us: use the live checks on the domain page to run the same probe from your own network and compare.
- The origin takes longer than 3s to send its first byte - real users see this as a slow site, not a broken one.
- A firewall DROPS our packets rather than refusing them. A refusal would have come back as "connection refused"; silence is what a drop rule looks like from outside.
- Traffic from datacenter or cloud networks is filtered. We egress from Cloudflare, which many origins treat differently from a residential connection.
- An AAAA record is published for an address that is not actually serving, so clients that prefer IPv6 hang.
- The origin only answers browser-like requests. We identify ourselves as DomainDrift rather than impersonating a browser.
These are the known causes, not a diagnosis of this domain. We recorded that nothing answered; we did not measure why.
Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS records 7
TLS certificates 0
None.
Subdomains 1
1 subdomain hostname observed and signed - the list itself is part of the paid record.
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_15af517565f0e502- Output Hash
3b7a5b6aa3c32a7e1002023c79ddda9078ab4a561e2244fd78f3d339070a4088- Signature
ed25519:0a7f4233e619aa7c6d88863aa2a542dc27d1ed5ab64c99ff508ce07ad1a755fe6e92b73b291768177d44435353bdccd51b89e66684c50f2176fa8b5e29972c09- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast