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.lobstr.co

Stellarstellarlobstr.co· horizon.stellarcompare ↔● PQ hybrid
Posture score
96
Speed score
82
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
http/1.1
Cert expires in
46d
Session resumed
yes
TLS handshake
21ms
Resumption
12ms
TTFB
716ms
RPC block height
65,570,019
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake21ms
Resumed?yes · 12ms
OCSP stapledno
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectlobstr.co
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANs*.stellar.lobstr.co, *.v1.stellar.lobstr.co, *.v2.stellar.lobstr.co +4
Not before2026-10-07
Not after2027-01-05
Days to expiry46d
Chain SHA-256f31f78f56a981d4b…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
B82
Certificate
100
TLS profile
96
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://horizon.stellar.lobstr.co
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_128_GCM_SHA256
Last seen
2026-11-20T00:55:42.317880341Z
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.lobstr.co'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:35.293Z
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.