https://rpc.numa.network/base

Baseevm

numa.network· 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

70d

Session resumed

yes

TLS handshake

1.86s

Resumption

1.15s

TTFB

RPC block height

Prober warning: phase_b: Post "https://rpc.numa.network/base": http2: timeout awaiting response headers

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake1.86s

Resumed?yes · 1.15s

OCSP stapledno

SCTs (CT log)none in TLS ext

PQ strict?no (classical tolerated)

Certificate chain

Subjectnuma.network

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsnuma.network, *.numa.network

Not before2026-10-03

Not after2027-01-01

Days to expiry70d

Chain SHA-2561e21c5cc84e8632b…

Modern posture

HSTSno header

HTTP/3 (ALPN hint)advertised in HTTPS record

ECH offeredyes · encrypted ClientHello published

DNSSECunsigned

CAA recordsnone published

Must-staplenot declared

Grades

Posture

C79

Speed

Certificate

100

TLS profile

Post-quantum

RPC reachability

Misconfigurations

OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL

https://rpc.numa.network/base

Host

rpc.numa.network

Chain

Base

Chain ID

8453

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-23T03:43:23.096675075Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

928ms

Latest block height

Current fastest URL

https://gateway.tenderly.co/public/base

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

Scan reportschema rpcscan-report · captured 2026-10-27T11:31:39.877Z

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.