RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Etherlink Mainnet

https://node.mainnet.etherlink.com

Etherlink Mainnetevmetherlink.com· node.mainnetcompare ↔● PQ hybrid
Posture score
96
Speed score
90
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
85d
Session resumed
yes
TLS handshake
59ms
Resumption
52ms
TTFB
502ms
RPC block height
58,185,468
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake59ms
Resumed?yes · 52ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectnode.mainnet.etherlink.com
IssuerWR1
Key typeRSA-2048
Chain length3
SANsnode.mainnet.etherlink.com, node.ghostnet.etherlink.com, node.shadownet.etherlink.com +3
Not before2026-11-12
Not after2027-02-10
Days to expiry85d
Chain SHA-256bb3eb92a6c2b17af…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+96
Speed
A90
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://node.mainnet.etherlink.com
Host
Chain ID
42793
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_256_GCM_SHA384
Last seen
2026-11-16T20:26:45.583268711Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
449ms
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 'https://node.mainnet.etherlink.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:20:28.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.