RPCScan
5,016 networks tracked8,091 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Stellar

https://rpc.ankr.com/http/stellar_horizon

Stellarstellarankr.com· rpccompare ↔● PQ hybrid
Posture score
96
Speed score
99
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
82d
Session resumed
yes
TLS handshake
20ms
Resumption
24ms
TTFB
296ms
RPC block height
65,570,019
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake20ms
Resumed?yes · 24ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectshark.multi-rpc.com
IssuerWR1
Key typeRSA-2048
Chain length3
SANsshark.multi-rpc.com, next.multi-rpc.com, rpc.ankr.com +1
Not before2026-11-12
Not after2027-02-10
Days to expiry82d
Chain SHA-256f2f6bb4ab6bda487…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
A+99
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://rpc.ankr.com/http/stellar_horizon
Host
Chain
Chain ID
-
VM
stellar
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_256_GCM_SHA384
Last seen
2026-11-20T00:55:42.520633825Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
227ms
Latest block height
-

Using this RPC

tabs auto-fill the URL
Generic JSON-RPC ping. Adjust the method to whatever the chain expects.
curl 'https://rpc.ankr.com/http/stellar_horizon'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:36.118Z
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.