https://rpc.hyperliquid-testnet.xyz/evm

Hyperliquid EVM Testnetevm

hyperliquid-testnet.xyz· rpc compare ↔● PQ hybrid

Posture score

Speed score

100

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

60d

Session resumed

yes

TLS handshake

32ms

Resumption

2ms

TTFB

311ms

RPC block height

66,309,435

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPN-

PQ classPQ hybrid

Handshake32ms

Resumed?yes · 2ms

OCSP stapledyes

SCTs presentno

Certificate chain

Subjecthyperliquid-testnet.xyz

IssuerAmazon RSA 2048 M04

Key typeRSA-2048

Chain length3

SANshyperliquid-testnet.xyz, *.hyperliquid-testnet.xyz

Not before2025-11-07

Not after2026-12-06

Days to expiry60d

Chain SHA-256f0da6fce72e84fa1…

Misconfigurations

ALPN not negotiated no_alpn

Grades

Posture

A+95

Speed

A+100

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.hyperliquid-testnet.xyz/evm

Host

rpc.hyperliquid-testnet.xyz

Chain

Hyperliquid EVM Testnet

Chain ID

998

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

PQ hybrid

Key exchange

X25519MLKEM768

Cipher

TLS_AES_128_GCM_SHA256

Last seen

2026-10-07T23:58:02.684740299Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:48:10.906Z

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.