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

https://rpc2.eoraptor.org

Eoraptorevmeoraptor.org· rpc2compare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
34
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
44d
Session resumed
yes
TLS handshake
344ms
Resumption
439ms
TTFB
2.35s
RPC block height
124,316
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake344ms
Resumed?yes · 439ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc2.eoraptor.org
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc2.eoraptor.org
Not before2026-09-11
Not after2026-12-10
Days to expiry44d
Chain SHA-256ef488c9c3c7bb028…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
F34
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc2.eoraptor.org
Host
Chain ID
2679
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_256_GCM_SHA384
Last seen
2026-10-27T06:49:03.812604462Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
2.35s
Latest block height
-
Current fastest URL
https://rpc2.eoraptor.org

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://rpc2.eoraptor.org' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T09:18:37.831Z
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.