RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
WEMIX3.0 Mainnet

wss://ws.wemix.com

WEMIX3.0 Mainnetevmwemix.com· wscompare ↔
Posture score
84
Speed score
77
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
115d
Session resumed
no
TLS handshake
-
Resumption
211ms
TTFB
-
RPC block height
128,626,735
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake-
Resumed?no
OCSP stapledyes
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subject*.wemix.com
IssuerSectigo Public Server Authentication CA DV R36
Key typeRSA-2048
Chain length4
SANs*.wemix.com, wemix.com
Not before2026-08-25
Not after2027-03-11
Days to expiry115d
Chain SHA-2565765d5e0da7ca6ab…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B84
Speed
C77
Certificate
100
TLS profile
97
Post-quantum
40
RPC reachability
100
Misconfigurations
● No issues detected.

Endpoint identity

URL
wss://ws.wemix.com
Host
Chain ID
1111
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-11-16T20:20:39.833160982Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
271ms
Latest block height
-
Current fastest URL
https://wemix.drpc.org

Using this RPC

tabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'wss://ws.wemix.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T23:36:42.437Z
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.