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

https://api.zan.top/polygon-mainnet

Polygon Mainnetevmzan.top· apicompare ↔
Posture score
61
Speed score
21
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
89d
Session resumed
no
TLS handshake
914ms
Resumption
766ms
TTFB
2.87s
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake914ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.zan.top
IssuerAliyun RSA TLS DV G1
Key typeRSA-2048
Chain length3
SANs*.zan.top, zan.top
Not before2026-06-23
Not after2027-01-07
Days to expiry89d
Chain SHA-256a0545b5a2e5ea2a8…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D61
Speed
F21
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://api.zan.top/polygon-mainnet
Host
Chain ID
137
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_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-10T06:52:42.12617371Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
791ms
Latest block height
-
Current fastest URL
https://polygon.drpc.org
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://api.zan.top/polygon-mainnet' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:54:56.534Z
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.