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

https://zksync-os-testnet-xsolla.zksync.dev

Xsolla ZK Testnetevmzksync.dev· zksync-os-testnet-xsollacompare ↔● fastest right now● PQ hybrid
Posture score
95
Speed score
48
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
56d
Session resumed
no
TLS handshake
294ms
Resumption
301ms
TTFB
2.10s
RPC block height
963,757
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake294ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectzksync-os-testnet-xsolla.zksync.dev
IssuerYR1
Key typeRSA-2048
Chain length3
SANszksync-os-testnet-xsolla.zksync.dev
Not before2026-09-12
Not after2026-12-11
Days to expiry56d
Chain SHA-256eecdbeb0cedb7f1a…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+95
Speed
F48
Certificate
100
TLS profile
90
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://zksync-os-testnet-xsolla.zksync.dev
Host
Chain ID
579029
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-15T18:58:01.263296362Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
2.10s
Latest block height
-
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://zksync-os-testnet-xsolla.zksync.dev' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:54:25.798Z
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.