jnpc.or.jp
Observed Aug 16, 2026, 08:23 UTC (12h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
CloudflareHTTPS probe
The site answered with a 5xx, so the edge and TLS are working and the application behind them is not.
It does NOT mean the domain or its DNS is misconfigured - the request got all the way to an application to fail there.
- The origin is erroring or mid-deploy.
- An upstream in front of the origin cannot reach it.
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
MX 2
10bgmgate1.biglobe.ne.jp10bgmgate2.biglobe.ne.jp
TXT 2
v=spf1 +ip4:52.69.75.20/32 +ip4:35.160.56.99/32 include:spf.biglobe.ne.jp -allv=DMARC1; p=none
NS 2
ns06.mesh.ad.jpns07.mesh.ad.jp
SOA 1
ns06.mesh.ad.jp hostmaster.mesh.ad.jp
TLS Certificates (0)
None.
Subdomains (2)
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 Receipt
- Receipt ID
rcpt_e66927a46c93c025- Output Hash
44602f0341c9d556ae74bb83bd307f4225df8beedd1d499eb47098ee7970c421- Signature
ed25519:1933e8100896e8faaa60e8e4396de4982d834db1ea03c8a8723db41b4b9b9037ff662a2f5da929b6acef9bc3ab40605f24edf0d7fb9a9504073687f3c77b8409- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast