https://endpoints.omniatech.io/v1/arbitrum/one/public

Arbitrum Oneevm

omniatech.io· endpoints compare ↔● PQ hybrid

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

41d

Session resumed

TLS handshake

56ms

Resumption

TTFB

601ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake56ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subjectomniatech.io

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsomniatech.io, *.omniatech.io

Not before2026-08-22

Not after2026-11-20

Days to expiry41d

Chain SHA-25604abcd1b1eb2bd2d…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

A91

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://endpoints.omniatech.io/v1/arbitrum/one/public

Host

endpoints.omniatech.io

Chain

Arbitrum One

Chain ID

42161

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

PQ hybrid

Key exchange

X25519MLKEM768

Cipher

TLS_AES_128_GCM_SHA256

Last seen

2026-10-10T06:34:02.079483061Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

199ms

Latest block height

Current fastest URL

https://arbitrum-one.public.blastapi.io

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://endpoints.omniatech.io/v1/arbitrum/one/public' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T06:43:30.034Z

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.