RPCScan
5,016 networks tracked8,091 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Sui Testnet

https://public-sui-testnet.rpcnode.dev

Sui Testnetsuirpcnode.dev· public-sui-testnetcompare ↔● PQ hybrid
Posture score
80
Speed score
95
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
60d
Session resumed
yes
TLS handshake
35ms
Resumption
55ms
TTFB
397ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake35ms
Resumed?yes · 55ms
OCSP stapledno
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpcnode.dev
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANs*.rpcnode.dev, rpcnode.dev
Not before2026-10-21
Not after2027-01-19
Days to expiry60d
Chain SHA-25658bd8bcd153d197c…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B80
Speed
A+95
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://public-sui-testnet.rpcnode.dev
Host
Chain ID
-
VM
sui
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-20T01:05:39.237640563Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
103ms
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://public-sui-testnet.rpcnode.dev'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:31.646Z
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.