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

https://klaytn.api.onfinality.io/public

Kaia Mainnetevmonfinality.io· klaytn.apicompare ↔
Posture score
83
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
88d
Session resumed
no
TLS handshake
14ms
Resumption
15ms
TTFB
76ms
RPC block height
229,417,717
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake14ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectklaytn.api.onfinality.io
IssuerYR1
Key typeRSA-2048
Chain length3
SANsklaytn.api.onfinality.io
Not before2026-10-08
Not after2027-01-06
Days to expiry88d
Chain SHA-256156d3cda0cbde6d6…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
A+100
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://klaytn.api.onfinality.io/public
Host
Chain ID
8217
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_AES_128_GCM_SHA256
Last seen
2026-10-10T08:18:48.295227959Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
71ms
Latest block height
-
Current fastest URL
https://klaytn.drpc.org
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://klaytn.api.onfinality.io/public' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T08:27:59.228Z
SHA-256 of canonical content
computed in your browser
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.