do-reg.jp
Observed 2026-07-14T19:27:21.725Z (15h ago). Every field below was attested with an Ed25519 signature at scan time.
Up right now
Runs onCloudflare
tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat do-reg.jp actually stands on - every host below is a signed observation
do-reg.jp
A / AAAA
203.183.220.196
Cloudflareserves the site
NS
ns4.do-reg.jpns2.do-reg.jpns1.do-reg.jpns3.do-reg.jp
do-reg.jpanswers its DNS
MX
mail.do-reg.jpmxi.do-reg.jp
do-reg.jpreceives its email
HTTPS probe
redirect
Redirecting (3xx) 301 → https://www.do-reg.jp/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time668 ms
DNS resolutionNOERROR
Redirect chain
https://www.do-reg.jp/Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS Records
A 1
203.183.220.196
MX 2
10mail.do-reg.jp200mxi.do-reg.jp
TXT 2
v=spf1 redirect=_spf.do-reg.jpv=DMARC1; p=none
NS 4
ns4.do-reg.jpns2.do-reg.jpns1.do-reg.jpns3.do-reg.jp
SOA 1
ns1.do-reg.jp hostmaster.do-reg.jp
TLS Certificates (0)
None.
Subdomains (10)
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; nothing leaves your machine.
Verify this receiptEd25519 Receipt
- Receipt ID
53bd4f03-d355-489f-825d-43ab5002641c- Output Hash
a78554910565f933e351740af63d2278b743fa9864f9831a1cb3bc5ab6bd73de- Signature
ed25519:acfc947a736ef136a6c6daa4e6cd2a661f630daa8f54f2c71ddd34e548cab437a5cd1fff9bd619fc6418b7ba7e0c28b42cd6c227169e0761c3f1d6ff42a4ae0a- Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b- Parent
(genesis)- Plane
- fast