https://rpc.eni.top

ENI Networkevm

eni.top· rpc compare ↔● fastest right now● 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

167d

Session resumed

TLS handshake

497ms

Resumption

503ms

TTFB

3.26s

RPC block height

569,410

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake497ms

Resumed?no

OCSP stapledyes

SCTs (CT log)none in TLS ext

PQ strict?no (classical tolerated)

Certificate chain

Subject*.eniac.network

IssuerAmazon RSA 2048 M01

Key typeRSA-2048

Chain length3

SANs*.eniac.network, eniac.network, *.eni.top +1

Not before2026-09-16

Not after2027-04-01

Days to expiry167d

Chain SHA-256dbc01276e23c911e…

Modern posture

HSTSno header

HTTP/3 (ALPN hint)no

ECH offeredno

DNSSECunsigned

CAA recordsnone published

Must-staplenot declared

Grades

Posture

A+96

Speed

F23

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Misconfigurations

● No issues detected.

Endpoint identity

URL

https://rpc.eni.top

Host

rpc.eni.top

Chain

ENI Network

Chain ID

263

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-16T23:44:44.903789239Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

YES

Fastest p50 latency

3.26s

Latest block height

Current fastest URL

https://rpc.eni.top

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

Scan reportschema rpcscan-report · captured 2026-10-17T00:05:47.701Z

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.