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

https://rpc.blockdaemon.mainnet.arc.io

Arcevmarc.io· rpc.blockdaemon.mainnetcompare ↔● PQ hybrid
Posture score
96
Speed score
86
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
no
TLS handshake
102ms
Resumption
113ms
TTFB
654ms
RPC block height
31,599,584
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake102ms
Resumed?no
OCSP stapledyes
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.blockdaemon.mainnet.arc.io
IssuerSectigo Public Server Authentication CA DV R36
Key typeRSA-4096
Chain length4
SANsrpc.blockdaemon.mainnet.arc.io, www.rpc.blockdaemon.mainnet.arc.io
Not before2026-06-10
Not after2026-12-25
Days to expiry39d
Chain SHA-256c82d39dc4ee31a84…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
B86
Certificate
100
TLS profile
97
Post-quantum
90
RPC reachability
100
Misconfigurations
● No issues detected.

Endpoint identity

URL
https://rpc.blockdaemon.mainnet.arc.io
Host
Chain
Chain ID
5042
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-11-16T20:41:05.366360341Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
317ms
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.blockdaemon.mainnet.arc.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:24:26.961Z
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.