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

wss://rpc.satelink.network/rpc/ws/polygon

Polygon Mainnetevmsatelink.network· rpccompare ↔● PQ hybrid
Posture score
80
Speed score
12
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
890ms
TTFB
-
RPC block height
-
Prober warning: ws: upgrade status 404
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNhttp/1.1
PQ classPQ hybrid
Handshake-
Resumed?yes · 890ms
OCSP stapledno
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectsatelink.network
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANs*.satelink.network, satelink.network
Not before2026-10-13
Not after2027-01-11
Days to expiry77d
Chain SHA-25680af88b60d623e24…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredyes · encrypted ClientHello published
DNSSECunsigned
CAA recordsissue:comodoca.com · issue:digicert.com; cansignhttpexchanges=yes +9
Must-staplenot declared
Grades
Posture
B80
Speed
F12
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
wss://rpc.satelink.network/rpc/ws/polygon
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-26T03:44:00.357515338Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.20s
Latest block height
-

Using this RPC

tabs 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.satelink.network/rpc/ws/polygon' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T12:11:45.597Z
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.