wss://rpc.jasmyscan.net/ws
Posture score
96
Speed score
96
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
82d
Session resumed
no
TLS handshake
72ms
Resumption
73ms
TTFB
366ms
RPC block height
8,442
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake72ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.jasmyscan.net
IssuerYR1
Key typeRSA-2048
Chain length3
SANsrpc.jasmyscan.net
Not before2026-09-30
Not after2026-12-29
Days to expiry82d
Chain SHA-2567ce4ad313f3d9d65…
Misconfigurations
- OCSP stapling not enabled
no_ocsp_staple
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
Class
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-07T23:57:54.341058703Z
History (30 days)
no history
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'wss://rpc.jasmyscan.net/ws' \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Scan reportschema rpcscan-report · captured 2026-10-10T05:49:34.353Z
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.