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

wss://evm-rpc-ws.nibiru.fi

Nibiru cataclysm-1evmnibiru.fi· evm-rpc-wscompare ↔● PQ hybrid
Posture score
96
Speed score
89
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
http/1.1
Cert expires in
49d
Session resumed
yes
TLS handshake
-
Resumption
98ms
TTFB
-
RPC block height
49,749,966
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake-
Resumed?yes · 98ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectrpc.nibiru.fi
IssuerYR2
Key typeRSA-2048
Chain length3
SANsevm-rpc-ws.nibiru.fi, evm-rpc.nibiru.fi, grpc.nibiru.fi +2
Not before2026-10-07
Not after2027-01-05
Days to expiry49d
Chain SHA-256f93ba7ccf9bcf742…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:amazon.com · issue:pki.goog +3
Must-staplenot declared
Grades
Posture
A+96
Speed
B89
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
wss://evm-rpc-ws.nibiru.fi
Host
Chain ID
6900
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_256_GCM_SHA384
Last seen
2026-11-16T20:26:11.925130252Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
542ms
Latest block height
-
Current fastest URL
https://evm-rpc.nibiru.fi

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://evm-rpc-ws.nibiru.fi' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T23:43:03.491Z
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.