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

https://node1-mainnet.maalscan.io/

MAAL Chainevmmaalscan.io· node1-mainnetcompare ↔● PQ hybrid
Posture score
96
Speed score
98
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
48d
Session resumed
yes
TLS handshake
14ms
Resumption
7ms
TTFB
314ms
RPC block height
13,158,388
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake14ms
Resumed?yes · 7ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectmaalscan.io
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsmaalscan.io, *.maalscan.io
Not before2026-08-27
Not after2026-11-25
Days to expiry48d
Chain SHA-25640abf8e1a4eb7877…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
A+96
Speed
A+98
Certificate
100
TLS profile
95
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://node1-mainnet.maalscan.io/
Host
Chain ID
786
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-08T15:47:57.391565202Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
285ms
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://node1-mainnet.maalscan.io/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:37:51.566Z
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.