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

https://rpc.kriptoaman.com

KriptoAman Mainnetevmkriptoaman.com· rpccompare ↔
Posture score
73
Speed score
52
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
http/1.1
Cert expires in
71d
Session resumed
yes
TLS handshake
260ms
Resumption
299ms
TTFB
1.08s
RPC block height
652,128
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNhttp/1.1
PQ classUnknown
Handshake260ms
Resumed?yes · 299ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.kriptoaman.com
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsrpc.kriptoaman.com
Not before2026-09-21
Not after2026-12-20
Days to expiry71d
Chain SHA-2560cbf141080f36a29…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
F52
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://rpc.kriptoaman.com
Host
Chain ID
22028
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
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T05:53:52.1341383Z
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://rpc.kriptoaman.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:56:25.053Z
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.