https://mainnet.telos.net/evm

Telos EVM Mainnetevm

telos.net· mainnet compare ↔● PQ hybrid

Posture score

Speed score

TLS version

0x0000

Cipher

0x0000

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

Session resumed

TLS handshake

348ms

Resumption

141ms

TTFB

2.29s

RPC block height

Prober warning: phase_b: Post "https://eosphere.io": remote error: tls: unrecognized name

TLS handshake

Version0x0000

Cipher0x0000

KEX groupX25519MLKEM768

ALPN-

PQ classPQ hybrid

Handshake348ms

Resumed?no

OCSP stapledno

SCTs presentno

Certificate chain

Subject-

Issuer-

Key type-

Chain length-

SANs-

Not before-

Not after-

Days to expiry-

Misconfigurations

TLS version older than 1.2 tls_too_old
ALPN not negotiated no_alpn
OCSP stapling not enabled no_ocsp_staple

Grades

Posture

F58

Speed

F21

Certificate

TLS profile

Post-quantum

RPC reachability

Endpoint identity

URL

https://mainnet.telos.net/evm

Host

mainnet.telos.net

Chain

Telos EVM Mainnet

Chain ID

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

0x0000

Last seen

2026-10-10T06:37:35.122571322Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

1.24s

Latest block height

Current fastest URL

https://rpc.telos.net

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

Scan reportschema rpcscan-report · captured 2026-10-10T06:51:51.252Z

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.