RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://www.toronet.org/rpc2/

Toronet Mainnetevmtoronet.orgcompare ↔
Posture score
58
Speed score
79
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
94d
Session resumed
yes
TLS handshake
216ms
Resumption
72ms
TTFB
778ms
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake216ms
Resumed?yes · 72ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.toronet.org
IssuerSectigo Public Server Authentication CA DV R36
Key typeRSA-2048
Chain length4
SANs*.toronet.org, toronet.org
Not before2026-06-28
Not after2027-01-12
Days to expiry94d
Chain SHA-2565579f4b1e4d28d7b…
Misconfigurations
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
F58
Speed
C79
Certificate
100
TLS profile
65
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://www.toronet.org/rpc2/
Host
Chain ID
77777
VM
evm
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_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-10T05:48:54.956933491Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
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://www.toronet.org/rpc2/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:52:24.316Z
SHA-256 of canonical content
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.