https://iotex.api.onfinality.io/public

IoTeX Network Mainnetevm

onfinality.io· iotex.api compare ↔

Posture score

Speed score

100

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

89d

Session resumed

yes

TLS handshake

24ms

Resumption

31ms

TTFB

174ms

RPC block height

53,214,457

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake24ms

Resumed?yes · 31ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectiotex.api.onfinality.io

IssuerYR1

Key typeRSA-2048

Chain length3

SANsiotex.api.onfinality.io

Not before2026-10-09

Not after2027-01-07

Days to expiry89d

Chain SHA-256a5d0ec4bc2451322…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

A+100

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://iotex.api.onfinality.io/public

Host

iotex.api.onfinality.io

Chain

IoTeX Network Mainnet

Chain ID

4689

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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

TLS_AES_128_GCM_SHA256

Last seen

2026-10-09T19:28:36.130676653Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

Using this RPCtabs 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://iotex.api.onfinality.io/public' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:52:15.873Z

SHA-256 of canonical content

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.