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

https://rpc.sepolia.linea.build

Linea Sepoliaevmlinea.build· rpc.sepoliacompare ↔
Posture score
84
Speed score
92
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
80d
Session resumed
no
TLS handshake
64ms
Resumption
90ms
TTFB
438ms
RPC block height
33,642,729
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake64ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.sepolia.linea.build
IssuerYR2
Key typeRSA-2048
Chain length3
SANs*.sepolia.linea.build
Not before2026-11-07
Not after2027-02-05
Days to expiry80d
Chain SHA-256c292af8c3d8ac75d…
Modern posture
HSTSyes · max-age 183d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsissue:amazon.com · issue:letsencrypt.org +4
Must-staplenot declared
Grades
Posture
B84
Speed
A92
Certificate
100
TLS profile
99
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.sepolia.linea.build
Host
Chain ID
59141
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_AES_256_GCM_SHA384
Last seen
2026-11-16T20:26:51.773826898Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
346ms
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.linea.build' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:43:38.978Z
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.