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

https://rpc.api.moonbeam.network

Moonbeamevmmoonbeam.network· rpc.apicompare ↔
Posture score
46
Speed score
100
TLS version
0x0000
Cipher
0x0000
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
-
Session resumed
no
TLS handshake
35ms
Resumption
-
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://rpc.api.moonbeam.network": remote error: tls: handshake failure
TLS handshake
Version0x0000
Cipher0x0000
KEX groupclassical
ALPN-
PQ classClassical only
Handshake35ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject-
Issuer-
Key type-
Chain length-
SANs-
Not before-
Not after-
Days to expiry-
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
F46
Speed
A+100
Certificate
80
TLS profile
35
Post-quantum
40
RPC reachability
30
Misconfigurations
  • TLS version older than 1.2tls_too_old
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.api.moonbeam.network
Host
Chain ID
1284
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
0x0000
Last seen
2026-11-16T20:20:42.080013147Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
297ms
Latest block height
-

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