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

https://eth-mainnet.g.alchemy.com/v2/demo

Ethereum Mainnetevmalchemy.com· eth-mainnet.gcompare ↔
Posture score
66
Speed score
67
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
38d
Session resumed
no
TLS handshake
205ms
Resumption
77ms
TTFB
949ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake205ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.g.alchemy.com
IssuerYR2
Key typeRSA-2048
Chain length3
SANs*.g.alchemy.com, mpp.alchemy.com, x402.alchemy.com
Not before2026-08-19
Not after2026-11-17
Days to expiry38d
Chain SHA-2562498b3e36481c723…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D66
Speed
D67
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://eth-mainnet.g.alchemy.com/v2/demo
Host
Chain ID
1
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-10-10T03:32:31.916533671Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
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://eth-mainnet.g.alchemy.com/v2/demo' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:59.997Z
SHA-256 of canonical content
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.