wss://testnet-rpc2.iopn.tech/ws

IOPN Testnetevm

iopn.tech· testnet-rpc2 compare ↔

Posture score

Speed score

100

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

http/1.1

Cert expires in

63d

Session resumed

yes

TLS handshake

47ms

Resumption

72ms

TTFB

192ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake47ms

Resumed?yes · 72ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjecttestnet-rpc2.iopn.tech

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANstestnet-rpc2.iopn.tech

Not before2026-09-11

Not after2026-12-10

Days to expiry63d

Chain SHA-2565bc5aba7be2d0297…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D66

Speed

A+100

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

wss://testnet-rpc2.iopn.tech/ws

Host

testnet-rpc2.iopn.tech

Chain

IOPN Testnet

Chain ID

984

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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-10-07T23:58:02.222371832Z

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 'wss://testnet-rpc2.iopn.tech/ws' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:52:51.443Z

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.