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

https://babel-api.mainnet.iotex.io

IoTeX Network Mainnetevmiotex.io· babel-api.mainnetcompare ↔● PQ hybrid
Posture score
97
Speed score
97
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
64d
Session resumed
yes
TLS handshake
38ms
Resumption
40ms
TTFB
332ms
RPC block height
54,515,257
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake38ms
Resumed?yes · 40ms
OCSP stapledno
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectbabel-api.mainnet.iotex.io
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsbabel-api.mainnet.iotex.io
Not before2026-10-22
Not after2027-01-20
Days to expiry64d
Chain SHA-256aa0af4cb050bebf7…
Modern posture
HSTSyes · max-age 180d
HTTP/3 (ALPN hint)advertised in HTTPS record
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsissue:amazon.com · issue:comodoca.com +10
Must-staplenot declared
Grades
Posture
A+97
Speed
A+97
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://babel-api.mainnet.iotex.io
Host
Chain ID
4689
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-16T20:26:04.627901566Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
308ms
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://babel-api.mainnet.iotex.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:25:23.247Z
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.