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

The Multi-Chain RPC Explorer

Browse chains, RPC endpoints, and providers like a block explorer for infrastructure. Continuously probed, ranked by latency × uptime × block freshness, served as open data.

AdYour ad here.
Advertise on RPCScan →
Networks tracked4,9763,581 mainnets · 1,395 testnets
RPC URLs8,031continuously probed for latency, freshness, uptime
RPC providers2,387unique domains across every public RPC we probePQ-protected endpoints4,651pure ML-KEM-1024 or hybrid ML-KEM (last 24h)
PQ adoption · last 24h · livefull tracker →
Pure PQ 0 (0.0%)Hybrid 4651 (78.9%)Classical 1246 (21.1%)
What's newfull feed →
Top mainnets by public RPCsBrowse all 4,976 networks →
Live ranking of the 10 mainnets with the most public RPC URLs in the catalogue right now. Updates every time the upstream catalogue does. RPCScan tracks 4,976 networks classified by type (Chains, DAGs, Subnets, DA-layers, Sequencers, Messaging fabrics) and by virtual machine (EVM, SVM, UTXO/Bitcoin-Script, CosmWasm, Substrate-WASM, XRPL, MoveVM, Cairo, and more).
#NetworkIDTypeVMCurrencyRPCs
1
Ethereum MainnetEthereum Mainnet
1ChainEVMETH83
2
BNB Smart Chain MainnetBNB Smart Chain Mainnet
56ChainEVMBNB50
3
Polygon MainnetPolygon Mainnet
137ChainEVMPOL42
4
Arbitrum OneArbitrum One
42161ChainEVMETH39
5
BaseBase
8453ChainEVMETH38
6
OP MainnetOP Mainnet
10ChainEVMETH36
7
EvmosEvmos
9001ChainEVMEVMOS33
8
Avalanche C-ChainAvalanche C-Chain
43114ChainEVMAVAX29
9
GnosisGnosis
100ChainEVMXDAI23
10
Fantom OperaFantom Opera
250ChainEVMFTM22

Why TLS & post-quantum posture matters for RPCs

(a fast classical RPC can still leak your traffic and forge state)
RPCs are a massive attack surface
Every wallet, dApp, and bot talks to an RPC. A compromised endpoint can return fake balances, fake nonces, fake gas, censor your transactions, or inject malicious contract addresses into wallet UIs. Most public RPCs are run on cheap VPSes behind basic CDNs by teams that treat TLS as an afterthought, so RPCScan continuously probes them so you don't have to take their word for it.
Harvest now, decrypt later
Classical key exchange (X25519, P-256, P-384) is recordable today and decryptable later by a sufficiently large quantum computer. Anyone who passively records your encrypted RPC traffic today (high-value wallets, MEV bots, institutional flows) can have it decrypted in three to seven years. PQ-hybrid groups (X25519MLKEM768) and pure ML-KEM mix in lattice-based key shares that survive that future attacker. Live adoption tracker →
TLS hygiene = operational maturity
The same operators who get TLS right (TLS 1.3, ECDSA, OCSP, SCTs, PQ hybrid) tend to be the same ones who patch faster, run better hardware, and have higher uptime. Conversely an RPC still serving an RSA-PKCS1 cert with no SCTs and no PQ is usually behind on more than just crypto. The score is a proxy for whether the team is paying attention.
See the leaderboard →
Real incidents, not theory
MyEtherWallet (BGP hijack, ~$152K, 2018). Curve.fi (registrar takeover, ~$575K, Aug 2022). Celer cBridge (BGP hijack, ~$240K, Aug 2022). Galxe (registrar compromise, ~$269K, Oct 2023). Atomic Wallet (suspected supply-chain, $100M+, Jun 2023). LastPass → Solana drains (~$35M, 2023). Each one is a documented post-mortem, not a hypothetical. Full case file →
How to read the scores. A fast endpoint isn't automatically a safe one. The composite TLS score blends key-exchange PQ class, cipher, leaf-cert key + signature alg, chain validity, TLS version, and ALPN, then subtracts up to 20 points for misconfigurations (no OCSP, no SCTs, expiring certs, broken chain). An A means hybrid PQ + ECDSA + clean cert hygiene; an F usually means classical key exchange and an RSA-PKCS1 cert, neither of which provides forward secrecy against a future quantum attacker. Open any RPC’s page for a per-component breakdown and a list of recommended fixes.
RPC URLUse RPCScan as your wallet RPC

Paste https://<chainId>.rpcscan.xyz into MetaMask or any wallet that takes a custom RPC URL. Requests route to the fastest healthy free endpoint for that chain in real time, with automatic failover.

https://1.rpcscan.xyzEthereum mainnet·https://8453.rpcscan.xyzBase·https://42161.rpcscan.xyzArbitrum One