https://testnet-rpc.orangechain.xyz

Orange Chain Testnetevm

orangechain.xyz· testnet-rpc compare ↔

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_256_GCM_SHA384

KEX group

PQ class

Unknown

ALPN

Cert expires in

59d

Session resumed

yes

TLS handshake

129ms

Resumption

121ms

TTFB

541ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX group-

ALPN-

PQ classUnknown

Handshake129ms

Resumed?yes · 121ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectbesthighyield.com

IssuerYE1

Key typeECDSA-P-256

Chain length4

SANs*.09320.hk, *.157885.club, *.32.orangechain.xyz +87

Not before2026-09-09

Not after2026-12-08

Days to expiry59d

Chain SHA-256b7b713fb4065b84d…

Misconfigurations

ALPN not negotiated no_alpn
OCSP stapling not enabled no_ocsp_staple

Grades

Posture

F53

Speed

C79

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://testnet-rpc.orangechain.xyz

Host

testnet-rpc.orangechain.xyz

Chain

Orange Chain Testnet

Chain ID

240515

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

Unknown

Key exchange

Cipher

TLS_AES_256_GCM_SHA384

Last seen

2026-10-10T05:48:58.988936562Z

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 'https://testnet-rpc.orangechain.xyz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

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

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.