RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Liquid Network

https://liquid.network

Liquid Networkbitcoin_rpcliquid.networkcompare ↔● fastest right now
Posture score
66
Speed score
90
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
141d
Session resumed
yes
TLS handshake
13ms
Resumption
26ms
TTFB
766ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake13ms
Resumed?yes · 26ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectmempool.space
IssuerSectigo Public Server Authentication CA OV R36
Key typeRSA-2048
Chain length3
SANsmempool.space, *.es1.mempool.space, *.fra.mempool.space +15
Not before2026-09-20
Not after2027-04-06
Days to expiry141d
Chain SHA-256256cece59fe295ed…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsissue:sectigo.com
Must-staplenot declared
Grades
Posture
D66
Speed
A90
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://liquid.network
Host
Chain ID
-
VM
bitcoin_rpc
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_AES_128_GCM_SHA256
Last seen
2026-11-16T20:57:43.756621816Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
766ms
Latest block height
-
Current fastest URL
https://liquid.network

Using this RPC

tabs auto-fill the URL
Generic JSON-RPC ping. Adjust the method to whatever the chain expects.
curl 'https://liquid.network'
Scan reportschema rpcscan-report · captured 2026-11-16T22:30:36.568Z
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.