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

https://palette-opennet.com:22000

Palette Chain Testnetevmpalette-opennet.comcompare ↔● fastest right now
Posture score
61
Speed score
48
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
150d
Session resumed
no
TLS handshake
472ms
Resumption
-
TTFB
1.51s
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake472ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectpalette-opennet.com
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANspalette-opennet.com
Not before2026-08-24
Not after2027-03-09
Days to expiry150d
Chain SHA-2560cfc0fb78727a2e6…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D61
Speed
F48
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://palette-opennet.com:22000
Host
Chain ID
17180
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
Classical only
Key exchange
-
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-10T06:54:01.413687733Z
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://palette-opennet.com:22000' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:58:56.763Z
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.