wss://openapi2.platon.network/ws

PlatON Mainnetevm

platon.network· openapi2 compare ↔

Posture score

Speed score

TLS version

TLS 1.2

Cipher

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

KEX group

classical

PQ class

Classical only

ALPN

http/1.1

Cert expires in

141d

Session resumed

yes

TLS handshake

463ms

Resumption

244ms

TTFB

1.51s

RPC block height

TLS handshake

VersionTLS 1.2

CipherTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

KEX groupclassical

ALPNhttp/1.1

PQ classClassical only

Handshake463ms

Resumed?yes · 244ms

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.platon.network

IssuerAlibaba Cloud GCC R46 AlphaSSL CA 2025

Key typeRSA-2048

Chain length3

SANs*.platon.network, platon.network

Not before2026-01-28

Not after2027-03-01

Days to expiry141d

Chain SHA-25630601c8d63ff08d7…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

D61

Speed

F51

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

wss://openapi2.platon.network/ws

Host

openapi2.platon.network

Chain

PlatON Mainnet

Chain ID

210425

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_ECDHE_RSA_WITH_AES_256_GCM_SHA384

Last seen

2026-10-10T05:44:09.36032655Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:48:52.386Z

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.