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

https://rpc.sepolia.org

Ethereum Sepoliaevmsepolia.org· rpccompare ↔● PQ hybrid
Posture score
79
Speed score
-
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
74d
Session resumed
yes
TLS handshake
120ms
Resumption
4ms
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://rpc.sepolia.org": http2: timeout awaiting response headers
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake120ms
Resumed?yes · 4ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectsepolia.org
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANssepolia.org, *.sepolia.org
Not before2026-10-06
Not after2027-01-04
Days to expiry74d
Chain SHA-256c08326daad67327c…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C79
Speed
F0
Certificate
100
TLS profile
97
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.sepolia.org
Host
Chain ID
11155111
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-10-22T00:26:21.690546042Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
992ms
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://rpc.sepolia.org' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:31:38.678Z
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.