https://api.stateless.solutions/arbitrum-one/v1/demo

Arbitrum Oneevm

stateless.solutions· api compare ↔

Posture score

Speed score

TLS version

0x0000

Cipher

0x0000

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

Session resumed

TLS handshake

1.27s

Resumption

TTFB

RPC block height

Prober warning: phase_b: Post "https://api.stateless.solutions/arbitrum-one/v1/demo": tls: failed to verify certificate: x509: certificate is valid for monitoring-cadu-bio.odin-vision.com, not api.stateless.solutions

TLS handshake

Version0x0000

Cipher0x0000

KEX groupclassical

ALPN-

PQ classClassical only

Handshake1.27s

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 recordsnone published

Must-staplenot declared

Grades

Posture

F44

Speed

Certificate

TLS profile

Post-quantum

RPC reachability

Misconfigurations

TLS version older than 1.2tls_too_old
ALPN not negotiatedno_alpn
OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL

https://api.stateless.solutions/arbitrum-one/v1/demo

Host

api.stateless.solutions

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

Classical only

Key exchange

Cipher

0x0000

Last seen

2026-10-24T03:45:11.6677831Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

1.13s

Latest block height

Current fastest URL

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

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

Scan reportschema rpcscan-report · captured 2026-10-27T11:35:40.366Z

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.