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

wss://mainnet.block.caduceus.foundation

CMP-Mainnetevmcaduceus.foundation· mainnet.blockcompare ↔
Posture score
36
Speed score
100
TLS version
0x0000
Cipher
0x0000
KEX group
-
PQ class
Unknown
ALPN
-
Cert expires in
-
Session resumed
no
TLS handshake
44ms
Resumption
-
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://mainnet.block.caduceus.foundation": tls: failed to verify certificate: x509: certificate is valid for *.iot.us-east-1.amazonaws.com, iot.us-east-1.amazonaws.com, not mainnet.block.caduceus.foundation
TLS handshake
Version0x0000
Cipher0x0000
KEX group-
ALPN-
PQ classUnknown
Handshake44ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject-
Issuer-
Key type-
Chain length-
SANs-
Not before-
Not after-
Days to expiry-
Misconfigurations
  • TLS version older than 1.2 tls_too_old
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
F36
Speed
A+100
Certificate
80
TLS profile
35
Post-quantum
0
RPC reachability
30
Endpoint identity
URL
wss://mainnet.block.caduceus.foundation
Host
Chain ID
256256
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
Unknown
Key exchange
-
Cipher
0x0000
Last seen
2026-10-10T05:48:59.016124914Z
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 'wss://mainnet.block.caduceus.foundation' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:49:32.838Z
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.