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

https://rpc.testnet.itxchain.com

ITX Testnetevmitxchain.com· rpc.testnetcompare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
91
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
88d
Session resumed
yes
TLS handshake
98ms
Resumption
92ms
TTFB
515ms
RPC block height
25,795
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake98ms
Resumed?yes · 92ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.testnet.itxchain.com
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc.testnet.itxchain.com
Not before2026-10-08
Not after2027-01-06
Days to expiry88d
Chain SHA-256e7178f710ab908d6…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
A91
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://rpc.testnet.itxchain.com
Host
Chain ID
5321
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_256_GCM_SHA384
Last seen
2026-10-10T07:33:38.88217627Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
-
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://rpc.testnet.itxchain.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:34:46.401Z
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.