https://rpc.kinto.xyz/http

Kinto Mainnetevm

kinto.xyz· 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

38d

Session resumed

yes

TLS handshake

14ms

Resumption

10ms

TTFB

298ms

RPC block height

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake14ms

Resumed?yes · 10ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc.kinto.xyz

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsrpc.kinto.xyz

Not before2026-08-19

Not after2026-11-17

Days to expiry38d

Chain SHA-2563cc6da7c74e4bb72…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

C78

Speed

A+99

Certificate

100

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://rpc.kinto.xyz/http

Host

rpc.kinto.xyz

Chain

Kinto Mainnet

Chain ID

7887

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-10T07:33:48.023049128Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

Latest block height

Current fastest URL

https://rpc.ankr.com/kinto

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

Scan reportschema rpcscan-report · captured 2026-10-10T07:39:15.020Z

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.