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

https://gnosis.oat.farm

Gnosisevmoat.farm· gnosiscompare ↔
Posture score
82
Speed score
7
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
89d
Session resumed
no
TLS handshake
898ms
Resumption
1.28s
TTFB
6.71s
RPC block height
48,946,173
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake898ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectgnosis.oat.farm
IssuerYR2
Key typeRSA-2048
Chain length3
SANsgnosis.oat.farm
Not before2026-10-25
Not after2027-01-23
Days to expiry89d
Chain SHA-256decdd32a484af066…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B82
Speed
F7
Certificate
100
TLS profile
90
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://gnosis.oat.farm
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
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-26T03:43:49.348334606Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
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://gnosis.oat.farm' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:33:23.227Z
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.