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

https://mainnet.innovunode.io/rpc

COTIevminnovunode.io· mainnetcompare ↔● fastest right now● PQ hybrid
Posture score
96
Speed score
72
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
87d
Session resumed
yes
TLS handshake
134ms
Resumption
144ms
TTFB
1.14s
RPC block height
9,989,756
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake134ms
Resumed?yes · 144ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectinnovunode.io
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsinnovunode.io, *.innovunode.io
Not before2026-10-19
Not after2027-01-17
Days to expiry87d
Chain SHA-256be18fc0583a931ff…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
C72
Certificate
100
TLS profile
97
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://mainnet.innovunode.io/rpc
Host
Chain
Chain ID
2632500
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-10-22T00:26:19.572132087Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
1.14s
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 'https://mainnet.innovunode.io/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:33:40.273Z
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.