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

https://starknet-sepolia.drpc.org

Starknet Sepoliastarknetdrpc.org· starknet-sepoliacompare ↔● PQ hybrid
Posture score
96
Speed score
63
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
71d
Session resumed
yes
TLS handshake
124ms
Resumption
40ms
TTFB
1.31s
RPC block height
17,352,734
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake124ms
Resumed?yes · 40ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectdrpc.org
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsdrpc.org, *.drpc.org
Not before2026-10-11
Not after2027-01-09
Days to expiry71d
Chain SHA-2562ac26defefd34310…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
D63
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://starknet-sepolia.drpc.org
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-29T23:22:43.205826387Z
History (30 days)
no history

Chain peer ranking

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

Using this RPC

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