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

https://rpc.xlayer.tech

X Layer Mainnetevmxlayer.tech· rpccompare ↔● PQ hybrid
Posture score
97
Speed score
81
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
63d
Session resumed
yes
TLS handshake
81ms
Resumption
40ms
TTFB
687ms
RPC block height
76,096,781
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake81ms
Resumed?yes · 40ms
OCSP stapledyes
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.xlayer.tech
IssuerGeoTrust TLS RSA CA G1
Key typeRSA-2048
Chain length2
SANs*.xlayer.tech, xlayer.tech
Not before2026-01-19
Not after2027-01-18
Days to expiry63d
Chain SHA-256f5a75157f3ce02bd…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+97
Speed
B81
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Misconfigurations
● No issues detected.

Endpoint identity

URL
https://rpc.xlayer.tech
Host
Chain ID
196
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-11-16T21:50:16.756397855Z
History (30 days)
no history

Chain peer ranking

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