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

https://rpc.gnosischain.com

Gnosisevmgnosischain.com· rpccompare ↔● fastest right now● PQ hybrid
Posture score
95
Speed score
59
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
PQ hybrid
ALPN
h2
Cert expires in
38d
Session resumed
yes
TLS handshake
230ms
Resumption
177ms
TTFB
1.42s
RPC block height
48,961,765
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classPQ hybrid
Handshake230ms
Resumed?yes · 177ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.gnosischain.com
IssuerWR3
Key typeRSA-2048
Chain length3
SANsrpc.gnosischain.com, rpc-gbc.gnosischain.com
Not before2026-09-05
Not after2026-12-04
Days to expiry38d
Chain SHA-2560f5e0181be8c90f5…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsiodef:mailto:devops@gnosis.io · issue:amazon.com +5
Must-staplenot declared
Grades
Posture
A+95
Speed
F59
Certificate
100
TLS profile
92
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.gnosischain.com
Host
Chain
Chain ID
100
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
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-27T01:43:16.925818257Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
1.42s
Latest block height
-
Current fastest URL
https://rpc.gnosischain.com

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.gnosischain.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:31:27.399Z
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.