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

https://s1.ripple.com:51234

XRP Ledgerxrplripple.com· s1compare ↔● PQ hybrid
Posture score
93
Speed score
76
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
-
Cert expires in
178d
Session resumed
no
TLS handshake
113ms
Resumption
86ms
TTFB
901ms
RPC block height
107,556,023
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPN-
PQ classPQ hybrid
Handshake113ms
Resumed?no
OCSP stapledno
SCTs presentno
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 expiry178d
Chain SHA-2562eeb6cd2b53c29e0…
Misconfigurations
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A93
Speed
C76
Certificate
100
TLS profile
85
Post-quantum
90
RPC reachability
100
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-10-10T06:54:12.025085075Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
-
Latest block height
-
Current fastest URL
https://xrplcluster.com
Using this RPCtabs 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-10-10T06:58:05.474Z
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.