RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://rpc-1.japanopenchain.org:8545

Japan Open Chain Mainnetevmjapanopenchain.org· rpc-1compare ↔
Posture score
78
Speed score
35
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
70d
Session resumed
no
TLS handshake
491ms
Resumption
566ms
TTFB
2.22s
RPC block height
26,358,316
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake491ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc-1.japanopenchain.org
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANsrpc-1.japanopenchain.org
Not before2026-06-02
Not after2026-12-16
Days to expiry70d
Chain SHA-2569be3ec3e6b3d0010…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
F35
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rpc-1.japanopenchain.org:8545
Host
Chain ID
81
VM
evm
Platform type
chain
Live probe (last 24 h)
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
TLS posture (post-quantum)full history →
Class
Classical only
Key exchange
-
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-07T23:57:36.788596279Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
Using this RPCtabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://rpc-1.japanopenchain.org:8545' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:58.853Z
SHA-256 of canonical content
computing…

The hash covers every field above the JSON serialization with sorted keys. Re-running this computation against the downloaded artifact must produce the same hash; that's how RPCScan's future on-chain proofs (rpcscanchain) will let anyone verify a published snapshot wasn't tampered with.