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

https://sixnet-rpc-evm.sixprotocol.net

Six Protocolevmsixprotocol.net· sixnet-rpc-evmcompare ↔
Posture score
83
Speed score
61
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
84d
Session resumed
yes
TLS handshake
159ms
Resumption
175ms
TTFB
1.52s
RPC block height
21,838,153
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake159ms
Resumed?yes · 175ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectsixnet-rpc-evm.sixprotocol.net
IssuerWR3
Key typeRSA-2048
Chain length3
SANssixnet-rpc-evm.sixprotocol.net
Not before2026-10-04
Not after2027-01-02
Days to expiry84d
Chain SHA-2565aa83f5b9e39482a…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
D61
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://sixnet-rpc-evm.sixprotocol.net
Host
Chain ID
98
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-10T05:37:39.705763708Z
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://sixnet-rpc-evm.sixprotocol.net' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:48:09.491Z
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.