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

https://rpc.gokite.ai

KiteAIevmgokite.ai· rpccompare ↔● fastest right now
Posture score
76
Speed score
100
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
95d
Session resumed
yes
TLS handshake
26ms
Resumption
21ms
TTFB
71ms
RPC block height
1,250,552
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake26ms
Resumed?yes · 21ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.gokite.ai
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANs*.gokite.ai
Not before2025-12-14
Not after2027-01-12
Days to expiry95d
Chain SHA-2563d40be895926f013…
Misconfigurations
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C76
Speed
A+100
Certificate
100
TLS profile
65
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rpc.gokite.ai
Host
Chain
Chain ID
2366
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-09T13:08:26.091460162Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
71ms
Latest block height
-
Current fastest URL
https://rpc.gokite.ai
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.gokite.ai' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:36:00.082Z
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.