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

https://zetachain-mainnet.g.allthatnode.com/archive/evm

ZetaChain Mainnetevmallthatnode.com· zetachain-mainnet.gcompare ↔
Posture score
83
Speed score
86
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
65d
Session resumed
no
TLS handshake
73ms
Resumption
74ms
TTFB
604ms
RPC block height
19,387,976
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake73ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.g.allthatnode.com
IssuerYR2
Key typeRSA-2048
Chain length3
SANs*.allthatnode.com, *.g.allthatnode.com, *.l.allthatnode.com
Not before2026-09-16
Not after2026-12-15
Days to expiry65d
Chain SHA-256a65af8be840e37a2…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B86
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://zetachain-mainnet.g.allthatnode.com/archive/evm
Host
Chain ID
7000
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
Classical only
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T05:08:46.52435748Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
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://zetachain-mainnet.g.allthatnode.com/archive/evm' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:52:35.629Z
SHA-256 of canonical content
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.