wss://rpc.coke.hydration.cloud

Hydrationevm

hydration.cloud· rpc.coke compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

PQ class

Unknown

ALPN

Cert expires in

32d

Session resumed

TLS handshake

263ms

Resumption

TTFB

1.01s

RPC block height

15,619,176

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX group-

ALPNh2

PQ classUnknown

Handshake263ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.coke.hydration.cloud

IssuerYR2

Key typeRSA-4096

Chain length3

SANsrpc.coke.hydration.cloud

Not before2026-08-13

Not after2026-11-11

Days to expiry32d

Chain SHA-25642e51393fdf76867…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C73

Speed

F52

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

wss://rpc.coke.hydration.cloud

Host

rpc.coke.hydration.cloud

Chain

Hydration

Chain ID

222222

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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

TLS_AES_128_GCM_SHA256

Last seen

2026-10-10T06:48:43.344072225Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

https://rpc.sin.hydration.cloud

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://rpc.coke.hydration.cloud' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T06:52:43.892Z

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.