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

wss://gm.monad.at.htw.tech

Monadevmhtw.tech· gm.monad.atcompare ↔
Posture score
60
Speed score
88
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
12d
Session resumed
yes
TLS handshake
-
Resumption
98ms
TTFB
-
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake-
Resumed?yes · 98ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectgm.monad.at.htw.tech
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsgm.monad.at.htw.tech
Not before2026-08-31
Not after2026-11-29
Days to expiry12d
Chain SHA-2562a73f65b04dd5d2a…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
D60
Speed
B88
Certificate
80
TLS profile
90
Post-quantum
40
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
wss://gm.monad.at.htw.tech
Host
Chain
Chain ID
143
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-11-16T21:55:12.967927837Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
259ms
Latest block height
-

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://gm.monad.at.htw.tech' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T23:39:00.349Z
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.