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

https://evm.aevachain.app

Aeva Mainnetevmaevachain.app· evmcompare ↔● fastest right now
Posture score
83
Speed score
38
TLS version
TLS 1.3
Cipher
TLS_CHACHA20_POLY1305_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
71d
Session resumed
yes
TLS handshake
336ms
Resumption
369ms
TTFB
2.08s
RPC block height
1,249,941
TLS handshake
VersionTLS 1.3
CipherTLS_CHACHA20_POLY1305_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake336ms
Resumed?yes · 369ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectevm.aevachain.app
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsevm.aevachain.app
Not before2026-09-26
Not after2026-12-25
Days to expiry71d
Chain SHA-256b9176d9effdbc284…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B83
Speed
F38
Certificate
100
TLS profile
92
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://evm.aevachain.app
Host
Chain ID
2383
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_CHACHA20_POLY1305_SHA256
Last seen
2026-10-15T18:56:52.306729997Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
2.08s
Latest block height
-
Current fastest URL
https://evm.aevachain.app
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.app' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:53:35.060Z
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.