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

https://aium-rpc-dev.viacube.com

AxelChain Dev-Netevmviacube.com· aium-rpc-devcompare ↔
Posture score
46
Speed score
58
TLS version
0x0000
Cipher
0x0000
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
-
Session resumed
no
TLS handshake
171ms
Resumption
-
TTFB
-
RPC block height
-
Prober warning: phase_b: Post "https://aium-rpc-dev.viacube.com": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-10T05:48:54Z is after 2025-02-16T06:58:08Z
TLS handshake
Version0x0000
Cipher0x0000
KEX groupclassical
ALPN-
PQ classClassical only
Handshake171ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject-
Issuer-
Key type-
Chain length-
SANs-
Not before-
Not after-
Days to expiry-
Misconfigurations
  • TLS version older than 1.2 tls_too_old
  • ALPN not negotiated no_alpn
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
F46
Speed
F58
Certificate
80
TLS profile
35
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://aium-rpc-dev.viacube.com
Host
Chain ID
61800
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
0x0000
Last seen
2026-10-10T05:48:53.165978566Z
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://aium-rpc-dev.viacube.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:51:50.825Z
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.