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

https://hydration-rpc.n.dwellir.com

Hydrationevmdwellir.com· hydration-rpc.ncompare ↔
Posture score
73
Speed score
70
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
82d
Session resumed
yes
TLS handshake
134ms
Resumption
111ms
TTFB
599ms
RPC block height
15,617,676
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX group-
ALPNh2
PQ classUnknown
Handshake134ms
Resumed?yes · 111ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjecthydration-rpc.n.dwellir.com
IssuerZeroSSL ECC DV SSL CA 2
Key typeECDSA-P-256
Chain length3
SANshydration-rpc.n.dwellir.com
Not before2026-10-02
Not after2026-12-31
Days to expiry82d
Chain SHA-256e41d78be0e6966fc…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
C70
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://hydration-rpc.n.dwellir.com
Host
Chain ID
222222
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
TLS_AES_256_GCM_SHA384
Last seen
2026-10-10T05:54:06.678238673Z
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 'https://hydration-rpc.n.dwellir.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:58:56.027Z
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.