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

https://hyperliquid.rpc.blxrbdn.com

Wanchain Testnetevmblxrbdn.com· hyperliquid.rpccompare ↔
Posture score
63
Speed score
9
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
140d
Session resumed
yes
TLS handshake
295ms
Resumption
289ms
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://hyperliquid.rpc.blxrbdn.com": EOF
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake295ms
Resumed?yes · 289ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.rpc.blxrbdn.com
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANs*.rpc.blxrbdn.com
Not before2026-01-26
Not after2027-02-24
Days to expiry140d
Chain SHA-256e62a64cfa28af47e…
Misconfigurations
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D63
Speed
F9
Certificate
100
TLS profile
85
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://hyperliquid.rpc.blxrbdn.com
Host
Chain ID
999
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
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-07T23:58:02.812143003Z
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://hyperliquid.rpc.blxrbdn.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:51:58.386Z
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.