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

https://evm.aevachain.com

Aeva Testnetevmaevachain.com· evmcompare ↔● fastest right now● PQ hybrid
Posture score
95
Speed score
40
TLS version
TLS 1.3
Cipher
TLS_CHACHA20_POLY1305_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
66d
Session resumed
yes
TLS handshake
287ms
Resumption
328ms
TTFB
2.00s
RPC block height
317,444
TLS handshake
VersionTLS 1.3
CipherTLS_CHACHA20_POLY1305_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake287ms
Resumed?yes · 328ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectevm.aevachain.com
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsevm.aevachain.com
Not before2026-09-22
Not after2026-12-21
Days to expiry66d
Chain SHA-256480712688d850b6b…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+95
Speed
F40
Certificate
100
TLS profile
92
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://evm.aevachain.com
Host
Chain ID
2382
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_CHACHA20_POLY1305_SHA256
Last seen
2026-10-15T18:56:52.30566091Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
2.00s
Latest block height
-
Current fastest URL
https://evm.aevachain.com
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://evm.aevachain.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:53:17.043Z
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.