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

https://fuse.liquify.com

Fuse Mainnetevmliquify.com· fusecompare ↔
Posture score
82
Speed score
65
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
20d
Session resumed
yes
TLS handshake
201ms
Resumption
203ms
TTFB
1.07s
RPC block height
45,159,177
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake201ms
Resumed?yes · 203ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
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 expiry20d
Chain SHA-2562530cae0c12d72f8…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B82
Speed
D65
Certificate
100
TLS profile
90
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://fuse.liquify.com
Host
Chain ID
122
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_128_GCM_SHA256
Last seen
2026-11-16T20:20:13.770650079Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
517ms
Latest block height
-
Current fastest URL
https://fuse.drpc.org

Using this RPC

tabs 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://fuse.liquify.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:28:54.536Z
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.