RPCScan
5,016 networks tracked8,091 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
TON

https://ton.api.onfinality.io/public/api/v2/jsonRPC

TONtononfinality.io· ton.apicompare ↔
Posture score
82
Speed score
99
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
87d
Session resumed
no
TLS handshake
11ms
Resumption
35ms
TTFB
279ms
RPC block height
106,578,530
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake11ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectton.api.onfinality.io
IssuerYR1
Key typeRSA-2048
Chain length3
SANston.api.onfinality.io
Not before2026-11-17
Not after2027-02-15
Days to expiry87d
Chain SHA-256e69debc77ad6069b…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B82
Speed
A+99
Certificate
100
TLS profile
90
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://ton.api.onfinality.io/public/api/v2/jsonRPC
Host
Chain
Chain ID
-
VM
ton
Platform type
chain

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_AES_128_GCM_SHA256
Last seen
2026-11-20T04:10:38.18717683Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
152ms
Latest block height
-

Using this RPC

tabs auto-fill the URL
Generic JSON-RPC ping. Adjust the method to whatever the chain expects.
curl 'https://ton.api.onfinality.io/public/api/v2/jsonRPC'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:36.916Z
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.