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.fuse.io

Fuse Mainnetevmfuse.io· rpccompare ↔
Posture score
84
Speed score
79
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
57d
Session resumed
no
TLS handshake
137ms
Resumption
96ms
TTFB
735ms
RPC block height
45,160,317
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake137ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.fuse.io
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc.fuse.io
Not before2026-10-15
Not after2027-01-13
Days to expiry57d
Chain SHA-25640043c676a0259a1…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:amazon.com · issue:letsencrypt.org +1
Must-staplenot declared
Grades
Posture
B84
Speed
C79
Certificate
100
TLS profile
96
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.fuse.io
Host
Chain ID
122
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_256_GCM_SHA384
Last seen
2026-11-16T21:55:10.496150185Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
517ms
Latest block height
-
Current fastest URL
https://fuse.drpc.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://rpc.fuse.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:31:08.415Z
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.