https://rpc.elysiumchain.us
Posture score
66
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
126d
Session resumed
no
TLS handshake
24ms
Resumption
15ms
TTFB
109ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake24ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.elysiumchain.tech
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANs*.elysiumchain.tech, elysiumchain.us, *.elysiumchain.us +1
Not before2026-07-28
Not after2027-02-10
Days to expiry126d
Chain SHA-256aac4334644338817…
Misconfigurations
- OCSP stapling not enabled
no_ocsp_staple
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
Class
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-07T23:58:09.182486082Z
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 'https://rpc.elysiumchain.us' \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Scan reportschema rpcscan-report · captured 2026-10-10T05:47:21.228Z
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.