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

https://testnet-node1.meronscan.ai/

Meroneum Testnetevmmeronscan.ai· testnet-node1compare ↔● PQ hybrid
Posture score
78
Speed score
92
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
55d
Session resumed
no
TLS handshake
96ms
Resumption
-
TTFB
467ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake96ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjecttestnet-node1.meronscan.ai
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANstestnet-node1.meronscan.ai
Not before2026-09-04
Not after2026-12-03
Days to expiry55d
Chain SHA-256de0388d299f2284e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
A92
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
30
Endpoint identity
URL
https://testnet-node1.meronscan.ai/
Host
Chain ID
3369
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-09T12:58:32.58454007Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
459ms
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://testnet-node1.meronscan.ai/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:57:21.104Z
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.