RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
BlueChain

https://rpc.chain.blue.org.mx

BlueChainevmorg.mx· rpc.chain.bluecompare ↔● fastest right now● PQ hybrid
Posture score
95
Speed score
42
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
63d
Session resumed
yes
TLS handshake
250ms
Resumption
295ms
TTFB
1.96s
RPC block height
12,787
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake250ms
Resumed?yes · 295ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.chain.blue.org.mx
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsrpc.chain.blue.org.mx
Not before2026-10-02
Not after2026-12-31
Days to expiry63d
Chain SHA-2563e05605ad46cdcbd…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+95
Speed
F42
Certificate
100
TLS profile
93
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.chain.blue.org.mx
Host
Chain ID
2583
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-10-29T06:04:06.839264899Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
1.96s
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.chain.blue.org.mx' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-29T08:25:01.735Z
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.