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

https://subnets.avax.network/dispatch/testnet/rpc

Dispatch L1evmavax.network· subnetscompare ↔● fastest right now● PQ hybrid
Posture score
95
Speed score
48
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
83d
Session resumed
yes
TLS handshake
217ms
Resumption
211ms
TTFB
1.54s
RPC block height
33,639
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake217ms
Resumed?yes · 211ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectsubnets.avax.network
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANssubnets.avax.network
Not before2026-10-09
Not after2027-01-07
Days to expiry83d
Chain SHA-256856cdb8b7c4603a4…
Modern posture
HSTSyes · max-age 0
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+95
Speed
F48
Certificate
100
TLS profile
93
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://subnets.avax.network/dispatch/testnet/rpc
Host
Chain ID
779672
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-15T18:58:03.139084906Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
1.54s
Latest block height
-
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://subnets.avax.network/dispatch/testnet/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:54:05.284Z
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.