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

https://testnet-rpc.ikchain.net

IKChain Testnetevmikchain.net· testnet-rpccompare ↔● fastest right now
Posture score
83
Speed score
87
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
56d
Session resumed
yes
TLS handshake
117ms
Resumption
115ms
TTFB
595ms
RPC block height
23,525
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake117ms
Resumed?yes · 115ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjecttestnet-rpc.ikchain.net
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANstestnet-rpc.ikchain.net
Not before2026-09-06
Not after2026-12-05
Days to expiry56d
Chain SHA-25606879137c2c4b9e6…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B87
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://testnet-rpc.ikchain.net
Host
Chain ID
4270
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-09T16:08:35.151483635Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
595ms
Latest block height
-
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://testnet-rpc.ikchain.net' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T09:04:44.755Z
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.