https://api.zan.top/public/starknet-mainnet

Starknetstarknet

zan.top· api compare ↔

Posture score

Speed score

TLS version

TLS 1.2

Cipher

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

70d

Session resumed

yes

TLS handshake

502ms

Resumption

230ms

TTFB

2.43s

RPC block height

17,149,323

TLS handshake

VersionTLS 1.2

CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake502ms

Resumed?yes · 230ms

OCSP stapledno

SCTs (CT log)none in TLS ext

PQ strict?no (classical tolerated)

Certificate chain

Subject*.zan.top

IssuerAliyun RSA TLS DV G1

Key typeRSA-2048

Chain length3

SANs*.zan.top, zan.top

Not before2026-06-23

Not after2027-01-07

Days to expiry70d

Chain SHA-256a0545b5a2e5ea2a8…

Modern posture

HSTSno header

HTTP/3 (ALPN hint)no

ECH offeredno

DNSSECunsigned

CAA recordsnone published

Must-staplenot declared

Grades

Posture

C77

Speed

F36

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Misconfigurations

OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL

https://api.zan.top/public/starknet-mainnet

Host

api.zan.top

Chain

Starknet

Chain ID

starknet

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

Classical only

Key exchange

Cipher

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Last seen

2026-10-29T23:22:43.016995045Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

Fastest p50 latency

1.16s

Latest block height

Current fastest URL

https://starknet-rpc.publicnode.com

Using this RPC

tabs auto-fill the URL

curl -X POST 'https://api.zan.top/public/starknet-mainnet' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"starknet_blockNumber","params":[]}'

Scan reportschema rpcscan-report · captured 2026-10-30T00:25:30.249Z

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.