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

https://qa-kwala-rpc-node.p2eppl.com

KWALA Stagenetevmp2eppl.com· qa-kwala-rpc-nodecompare ↔
Posture score
66
Speed score
66
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
182d
Session resumed
no
TLS handshake
219ms
Resumption
203ms
TTFB
1.18s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake219ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectp2eppl.com
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANsp2eppl.com, www.p2eppl.com, *.p2eppl.com
Not before2026-09-24
Not after2027-04-09
Days to expiry182d
Chain SHA-256b3922e5dbecb681e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D66
Speed
D66
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://qa-kwala-rpc-node.p2eppl.com
Host
Chain ID
1906
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-09T18:33:17.057300604Z
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://qa-kwala-rpc-node.p2eppl.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:05.754Z
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.