https://api.lcserve.org
Posture score
83
Speed score
52
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
64d
Session resumed
yes
TLS handshake
287ms
Resumption
210ms
TTFB
1.52s
RPC block height
13,798,305
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake287ms
Resumed?yes · 210ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectlcserve.org
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsapi.lcserve.org, lcserve.org
Not before2026-09-13
Not after2026-12-12
Days to expiry64d
Chain SHA-25612d9bcee587e1276…
Misconfigurations
- OCSP stapling not enabled
no_ocsp_staple
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
Class
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-08T18:02:33.342723593Z
History (30 days)
no history
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://api.lcserve.org' \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Scan reportschema rpcscan-report · captured 2026-10-10T05:50:56.140Z
SHA-256 of canonical content
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.