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

wss://wss.cchain.cc

CChainevmcchain.cc· wsscompare ↔
Posture score
66
Speed score
60
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
150d
Session resumed
yes
TLS handshake
255ms
Resumption
228ms
TTFB
1.29s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake255ms
Resumed?yes · 228ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.cchain.cc
IssuerGlobalSign GCC R6 AlphaSSL CA 2025
Key typeRSA-2048
Chain length3
SANs*.cchain.cc, cchain.cc
Not before2026-02-05
Not after2027-03-09
Days to expiry150d
Chain SHA-256802dfd9f36a6b2ac…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D66
Speed
D60
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
wss://wss.cchain.cc
Host
Chain
Chain ID
2500
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_256_GCM_SHA384
Last seen
2026-10-09T19:08:32.847260869Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
775ms
Latest block height
-
Current fastest URL
https://rpc.cchain.cc
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 'wss://wss.cchain.cc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:48:12.549Z
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.