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

https://s1.ripple.com:51234

XRP Ledgerxrplripple.com· s1compare ↔● PQ hybrid
Posture score
93
Speed score
81
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
-
Cert expires in
141d
Session resumed
no
TLS handshake
97ms
Resumption
86ms
TTFB
709ms
RPC block height
108,374,927
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPN-
PQ classPQ hybrid
Handshake97ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.ripple.com
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANs*.ripple.com, ripple.com
Not before2026-09-21
Not after2027-04-06
Days to expiry141d
Chain SHA-2562eeb6cd2b53c29e0…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:amazon.com · issue:digicert.com +6
Must-staplenot declared
Grades
Posture
A93
Speed
B81
Certificate
100
TLS profile
82
Post-quantum
90
RPC reachability
100
Misconfigurations
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://s1.ripple.com:51234
Host
Chain ID
-
VM
xrpl
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:57:49.883128177Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
600ms
Latest block height
-
Current fastest URL
https://xrplcluster.com

Using this RPC

tabs auto-fill the URL
import { Client } from 'xrpl';

const client = new Client('https://s1.ripple.com:51234');
await client.connect();
const info = await client.request({ command: 'server_info' });
await client.disconnect();
console.log(info.result.info.complete_ledgers);
Scan reportschema rpcscan-report · captured 2026-11-16T22:27:02.342Z
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.