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

https://base-sepolia.api.onfinality.io/public

Base Sepolia Testnetevmonfinality.io· base-sepolia.apicompare ↔
Posture score
73
Speed score
83
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
89d
Session resumed
no
TLS handshake
114ms
Resumption
63ms
TTFB
530ms
RPC block height
47,931,720
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classUnknown
Handshake114ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectbase-sepolia.api.onfinality.io
IssuerYR1
Key typeRSA-2048
Chain length3
SANsbase-sepolia.api.onfinality.io
Not before2026-10-09
Not after2027-01-07
Days to expiry89d
Chain SHA-256d980e18faaf5bd83…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
B83
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://base-sepolia.api.onfinality.io/public
Host
Chain ID
84532
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
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T11:28:50.00817359Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
-
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://base-sepolia.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-10T11:30:30.502Z
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.