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

https://u0tnafcv6j:o2T045sxuCNXL878RDQLp5__Zj-es2cvdjtgkl4etn0@u0v7kwtvtg-u0wj114sve-rpc.us0-aws.kaleido.io

SiriusNetevmkaleido.io· u0v7kwtvtg-u0wj114sve-rpc.us0-awscompare ↔● fastest right now
Posture score
57
Speed score
-
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
119d
Session resumed
no
TLS handshake
4.83s
Resumption
-
TTFB
23.79s
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake4.83s
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectkaleido.io
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANskaleido.io, *.kaleido.io, *.us0-aws.kaleido.io +2
Not before2026-01-21
Not after2027-02-18
Days to expiry119d
Chain SHA-256247257b8c51314d0…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
F57
Speed
F0
Certificate
100
TLS profile
58
Post-quantum
40
RPC reachability
30
Misconfigurations
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://u0tnafcv6j:o2T045sxuCNXL878RDQLp5__Zj-es2cvdjtgkl4etn0@u0v7kwtvtg-u0wj114sve-rpc.us0-aws.kaleido.io
Host
Chain ID
67390
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_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-22T03:43:16.967279209Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
23.79s
Latest block height
-

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://u0tnafcv6j:o2T045sxuCNXL878RDQLp5__Zj-es2cvdjtgkl4etn0@u0v7kwtvtg-u0wj114sve-rpc.us0-aws.kaleido.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:36:13.783Z
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.