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

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

Starknetstarknetonfinality.io· starknet.apicompare ↔
Posture score
82
Speed score
63
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
44d
Session resumed
no
TLS handshake
158ms
Resumption
47ms
TTFB
1.35s
RPC block height
17,149,323
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake158ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectstarknet.api.onfinality.io
IssuerYR2
Key typeRSA-2048
Chain length3
SANsstarknet.api.onfinality.io
Not before2026-09-14
Not after2026-12-13
Days to expiry44d
Chain SHA-256060374f18c039097…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B82
Speed
D63
Certificate
100
TLS profile
90
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://starknet.api.onfinality.io/public
Host
Chain ID
-
VM
starknet
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-29T23:22:43.075157097Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.16s
Latest block height
-

Using this RPC

tabs auto-fill the URL
curl -X POST 'https://starknet.api.onfinality.io/public' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"starknet_blockNumber","params":[]}'
Scan reportschema rpcscan-report · captured 2026-10-30T00:22:21.215Z
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.