RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://kava.api.pocket.network

Kavaevmpocket.network· kava.apicompare ↔● PQ hybrid
Posture score
96
Speed score
79
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
88d
Session resumed
yes
TLS handshake
202ms
Resumption
197ms
TTFB
823ms
RPC block height
23,523,665
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake202ms
Resumed?yes · 197ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.api.pocket.network
IssuerYR1
Key typeRSA-2048
Chain length3
SANs*.api.pocket.network, *.beta.api.pocket.network, *.paid.beta.api.pocket.network
Not before2026-11-15
Not after2027-02-13
Days to expiry88d
Chain SHA-256db9e9f41383b44c8…
Modern posture
HSTSyes · max-age 183d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:globalsign.com · issue:letsencrypt.org +2
Must-staplenot declared
Grades
Posture
A+96
Speed
C79
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://kava.api.pocket.network
Host
Chain
Chain ID
2222
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-11-16T17:56:22.957893629Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
167ms
Latest block height
-
Current fastest URL
https://evm.kava.io

Using this RPC

tabs 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://kava.api.pocket.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:23:45.841Z
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.