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

https://rpc.eoraptor.org

Eoraptorevmeoraptor.org· rpccompare ↔● PQ hybrid
Posture score
96
Speed score
33
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
39d
Session resumed
yes
TLS handshake
391ms
Resumption
444ms
TTFB
2.48s
RPC block height
124,316
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake391ms
Resumed?yes · 444ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.eoraptor.org
IssuerYR1
Key typeRSA-2048
Chain length3
SANsrpc.eoraptor.org
Not before2026-09-07
Not after2026-12-06
Days to expiry39d
Chain SHA-2564153ffd8618b064b…
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
F33
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://rpc.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.813579571Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
2.35s
Latest block height
-
Current fastest URL
https://rpc2.eoraptor.org
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://rpc.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:17:32.594Z
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.