RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
edeXa Mainnet

https://rpc.edexa.com

edeXa Mainnetevmedexa.com· rpccompare ↔
Posture score
83
Speed score
59
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
76d
Session resumed
yes
TLS handshake
422ms
Resumption
376ms
TTFB
1.19s
RPC block height
10,414,049
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake422ms
Resumed?yes · 376ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.edexa.network
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc.edexa.com, rpc.edexa.network
Not before2026-11-03
Not after2027-02-01
Days to expiry76d
Chain SHA-25633f3351fd5faf5df…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B83
Speed
F59
Certificate
100
TLS profile
93
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.edexa.com
Host
Chain ID
5424
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-11-16T18:21:13.19242882Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.17s
Latest block height
-
Current fastest URL
https://rpc.edexa.network

Using this RPC

tabs 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.edexa.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:31:04.786Z
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.