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

https://rpc.frax.com

Fraxtalevmfrax.com· rpccompare ↔● fastest right now● PQ hybrid
Posture score
97
Speed score
99
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
61d
Session resumed
yes
TLS handshake
29ms
Resumption
53ms
TTFB
327ms
RPC block height
44,024,855
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake29ms
Resumed?yes · 53ms
OCSP stapledno
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectfrax.com
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANs*.frax.com, frax.com
Not before2026-10-19
Not after2027-01-17
Days to expiry61d
Chain SHA-25651f54256be57a8bd…
Modern posture
HSTSyes · max-age 180d
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsissue:comodoca.com · issue:digicert.com; cansignhttpexchanges=yes +8
Must-staplenot declared
Grades
Posture
A+97
Speed
A+99
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.frax.com
Host
Chain
Chain ID
252
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_128_GCM_SHA256
Last seen
2026-11-16T20:20:21.752023776Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
327ms
Latest block height
-
Current fastest URL
https://rpc.frax.com

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