https://mode-mainnet.rpc.sentio.xyz

Modeevm

sentio.xyz· mode-mainnet.rpc 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

84d

Session resumed

yes

TLS handshake

56ms

Resumption

106ms

TTFB

576ms

RPC block height

45,722,025

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake56ms

Resumed?yes · 106ms

OCSP stapledno

SCTs presentno

Certificate chain

Subject*.rpc.sentio.xyz

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANs*.rpc.sentio.xyz, rpc.sentio.xyz

Not before2026-10-04

Not after2027-01-02

Days to expiry84d

Chain SHA-256c7171368fc06f1a7…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

A+96

Speed

B86

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://mode-mainnet.rpc.sentio.xyz

Host

mode-mainnet.rpc.sentio.xyz

Chain

Mode

Chain ID

34443

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-10T05:53:53.840077324Z

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://mode-mainnet.rpc.sentio.xyz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:59:38.855Z

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.