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

https://rpc.denergytestnet.com/

Denergy Testnetevmdenergytestnet.com· rpccompare ↔● fastest right now
Posture score
66
Speed score
-
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
62d
Session resumed
yes
TLS handshake
215ms
Resumption
207ms
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://rpc.denergytestnet.com/": http2: timeout awaiting response headers
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake215ms
Resumed?yes · 207ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.denergytestnet.com
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsrpc.denergytestnet.com
Not before2026-09-13
Not after2026-12-12
Days to expiry62d
Chain SHA-256e29a41f9500ef68e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D66
Speed
F0
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://rpc.denergytestnet.com/
Host
Chain ID
4442
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-10T08:58:36.914265818Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
1.09s
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://rpc.denergytestnet.com/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T09:04:18.916Z
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.