https://gwan-ssl.wandevs.org:46891/

Wanchain Testnetevm

wandevs.org· gwan-ssl 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

Cert expires in

88d

Session resumed

yes

TLS handshake

192ms

Resumption

96ms

TTFB

597ms

RPC block height

45,351,865

TLS handshake

VersionTLS 1.2

CipherTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake192ms

Resumed?yes · 96ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectgwan-ssl.wandevs.org

IssuerYR2

Key typeRSA-2048

Chain length3

SANsgwan-ssl.wandevs.org

Not before2026-10-06

Not after2027-01-04

Days to expiry88d

Chain SHA-2569130f9d9338e556d…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

B82

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://gwan-ssl.wandevs.org:46891/

Host

gwan-ssl.wandevs.org

Chain

Wanchain Testnet

Chain ID

999

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

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

168ms

Latest block height

Current fastest URL

https://hyperliquid-json-rpc.stakely.io

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://gwan-ssl.wandevs.org:46891/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T07:42:01.997Z

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.