RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://zircuit1-mainnet.liquify.com

Zircuit Mainnetevmliquify.com· zircuit1-mainnetcompare ↔
Posture score
63
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
57d
Session resumed
yes
TLS handshake
38ms
Resumption
36ms
TTFB
235ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPN-
PQ classClassical only
Handshake38ms
Resumed?yes · 36ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.liquify.com
IssuerSectigo Public Server Authentication CA DV R36
Key typeRSA-2048
Chain length4
SANs*.liquify.com, liquify.com
Not before2025-11-28
Not after2026-12-06
Days to expiry57d
Chain SHA-2562530cae0c12d72f8…
Misconfigurations
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D63
Speed
A+100
Certificate
100
TLS profile
85
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://zircuit1-mainnet.liquify.com
Host
Chain ID
48900
VM
evm
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_256_GCM_SHA384
Last seen
2026-10-10T05:53:57.683023713Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
Using this RPCtabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://zircuit1-mainnet.liquify.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:30.218Z
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.