https://sepolia.mode.network

Mode Testnetevm

mode.network· sepolia 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

53d

Session resumed

yes

TLS handshake

16ms

Resumption

6ms

TTFB

309ms

RPC block height

51,774,774

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake16ms

Resumed?yes · 6ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectsepolia.mode.network

IssuerYE2

Key typeECDSA-P-256

Chain length4

SANssepolia.mode.network

Not before2026-09-01

Not after2026-11-30

Days to expiry53d

Chain SHA-2566bf04191627005ea…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

A+96

Speed

A+99

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://sepolia.mode.network

Host

sepolia.mode.network

Chain

Mode Testnet

Chain ID

919

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-07T23:58:01.047915788Z

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

Scan reportschema rpcscan-report · captured 2026-10-10T05:57:32.419Z

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.