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

https://mainnet-rpc.sardisnetwork.com

Sardis Mainnetevmsardisnetwork.com· mainnet-rpccompare ↔● PQ hybrid
Posture score
78
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
39d
Session resumed
yes
TLS handshake
56ms
Resumption
32ms
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://mainnet-rpc.sardisnetwork.com": http2: timeout awaiting response headers
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake56ms
Resumed?yes · 32ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectsardisnetwork.com
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANssardisnetwork.com, *.sardisnetwork.com
Not before2026-08-20
Not after2026-11-18
Days to expiry39d
Chain SHA-256b3beed71cb21d03e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
F0
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
30
Endpoint identity
URL
https://mainnet-rpc.sardisnetwork.com
Host
Chain ID
51712
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-10T05:53:58.204076908Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
Using this RPCtabs 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://mainnet-rpc.sardisnetwork.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:58:22.499Z
SHA-256 of canonical content
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.