RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

wss://odyssey.nownodes.io/wss

Odyssey Chain (Testnet)evmnownodes.io· odysseycompare ↔● PQ hybrid
Posture score
77
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
http/1.1
Cert expires in
76d
Session resumed
yes
TLS handshake
-
Resumption
19ms
TTFB
-
RPC block height
-
Prober warning: ws: upgrade status 404
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake-
Resumed?yes · 19ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectnownodes.io
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsnownodes.io, *.nownodes.io
Not before2026-11-03
Not after2027-02-01
Days to expiry76d
Chain SHA-2568095f86f1df35070…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C77
Speed
A+100
Certificate
100
TLS profile
90
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
wss://odyssey.nownodes.io/wss
Host
Chain ID
131313
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-11-16T20:37:00.452722784Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
342ms
Latest block height
-

Using this RPC

tabs 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://odyssey.nownodes.io/wss' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T23:43:19.521Z
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.