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

https://rpc.swiftnodes.io/rpc/berachain

Berachainevmswiftnodes.io· rpccompare ↔
Posture score
83
Speed score
85
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
44d
Session resumed
no
TLS handshake
108ms
Resumption
139ms
TTFB
719ms
RPC block height
28,926,347
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake108ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.swiftnodes.io
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsrpc.swiftnodes.io
Not before2026-10-02
Not after2026-12-31
Days to expiry44d
Chain SHA-2567b923f3813403a65…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B83
Speed
B85
Certificate
100
TLS profile
92
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.swiftnodes.io/rpc/berachain
Host
Chain ID
80094
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-16T22:16:53.284522066Z
History (30 days)
no history

Chain peer ranking

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