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://horizon.stellar.org

Stellarstellarstellar.org· horizoncompare ↔
Posture score
74
Speed score
99
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
124d
Session resumed
no
TLS handshake
61ms
Resumption
48ms
TTFB
272ms
RPC block height
65,570,019
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake61ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.stellar.org
IssuerSectigo Public Server Authentication CA DV R36
Key typeRSA-2048
Chain length3
SANs*.stellar.org, stellar.org
Not before2026-09-07
Not after2027-03-24
Days to expiry124d
Chain SHA-2566f65b18bdc8c1eee…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C74
Speed
A+99
Certificate
100
TLS profile
58
Post-quantum
40
RPC reachability
100
Misconfigurations
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://horizon.stellar.org
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
Classical only
Key exchange
-
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-11-20T00:55:42.310844965Z
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://horizon.stellar.org'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:31.522Z
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.