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

https://evm-rpc.testnet.humans.zone

Humans.ai Testnetevmhumans.zone· evm-rpc.testnetcompare ↔● fastest right now
Posture score
66
Speed score
81
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
54d
Session resumed
yes
TLS handshake
128ms
Resumption
123ms
TTFB
749ms
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake128ms
Resumed?yes · 123ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectevm-rpc.testnet.humans.zone
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsevm-rpc.testnet.humans.zone
Not before2026-09-03
Not after2026-12-02
Days to expiry54d
Chain SHA-2569ff2635f928e94e4…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D66
Speed
B81
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://evm-rpc.testnet.humans.zone
Host
Chain ID
4139
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_AES_128_GCM_SHA256
Last seen
2026-10-09T16:08:33.919929211Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
749ms
Latest block height
-
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://evm-rpc.testnet.humans.zone' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:42:45.139Z
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.