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

https://x1-fastnet.xen.network

X1 Fastnetevmxen.network· x1-fastnetcompare ↔
Posture score
45
Speed score
70
TLS version
0x0000
Cipher
0x0000
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
-
Session resumed
no
TLS handshake
441ms
Resumption
-
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://x1-fastnet.xen.network": EOF
TLS handshake
Version0x0000
Cipher0x0000
KEX groupclassical
ALPN-
PQ classClassical only
Handshake441ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject-
Issuer-
Key type-
Chain length-
SANs-
Not before-
Not after-
Days to expiry-
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:globalsign.com · issue:letsencrypt.org +2
Must-staplenot declared
Grades
Posture
F45
Speed
C70
Certificate
80
TLS profile
30
Post-quantum
40
RPC reachability
30
Misconfigurations
  • TLS version older than 1.2tls_too_old
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://x1-fastnet.xen.network
Host
Chain ID
4003
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
0x0000
Last seen
2026-11-16T17:56:31.443748255Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
132ms
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://x1-fastnet.xen.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:44:23.780Z
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.