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

wss://rpc.mersennet.com

Mersennet Testnetevmmersennet.com· rpccompare ↔● PQ hybrid
Posture score
80
Speed score
56
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
77d
Session resumed
yes
TLS handshake
-
Resumption
203ms
TTFB
-
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake-
Resumed?yes · 203ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectmersennet.com
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsmersennet.com, *.mersennet.com
Not before2026-10-02
Not after2026-12-31
Days to expiry77d
Chain SHA-256ef5b3ad9223e637d…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B80
Speed
F56
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
wss://rpc.mersennet.com
Host
Chain ID
131071
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-15T18:57:53.401627384Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
2.18s
Latest block height
-
Current fastest URL
https://rpc.mersennet.com
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 'wss://rpc.mersennet.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-15T21:56:00.462Z
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.