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

https://edgeware-evm3.jelliedowl.net

Edgeware EdgeEVM Mainnetevmjelliedowl.net· edgeware-evm3compare ↔
Posture score
66
Speed score
-
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
65d
Session resumed
yes
TLS handshake
219ms
Resumption
215ms
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://edgeware-evm3.jelliedowl.net": net/http: timeout awaiting response headers
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake219ms
Resumed?yes · 215ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectedgeware-boot3.jelliedowl.net
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsedgeware-boot3.jelliedowl.net, edgeware-evm3.jelliedowl.net, edgeware-rpc3.jelliedowl.net
Not before2026-09-14
Not after2026-12-13
Days to expiry65d
Chain SHA-2561c5c6dec422517a8…
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://edgeware-evm3.jelliedowl.net
Host
Chain ID
2021
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_256_GCM_SHA384
Last seen
2026-10-09T13:08:19.944088312Z
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://edgeware-evm3.jelliedowl.net' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:00:04.429Z
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.