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

https://rpc-uat.evm.mirasmanda.uz

Mirasmanda UATevmmirasmanda.uz· rpc-uat.evmcompare ↔● fastest right now● PQ hybrid
Posture score
97
Speed score
81
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
39d
Session resumed
yes
TLS handshake
33ms
Resumption
29ms
TTFB
688ms
RPC block height
2,044,368
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake33ms
Resumed?yes · 29ms
OCSP stapledyes
SCTs (CT log)2 embedded
PQ strict?no (classical tolerated)
Certificate chain
Subjectmirasmanda.uz
IssuerCloudflare TLS Issuing ECC CA 3
Key typeECDSA-P-256
Chain length4
SANsmirasmanda.uz, *.mirasmanda.uz, *.evm.mirasmanda.uz +5
Not before2026-09-26
Not after2026-12-26
Days to expiry39d
Chain SHA-256199040dd4b1875fa…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+97
Speed
B81
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Misconfigurations
● No issues detected.

Endpoint identity

URL
https://rpc-uat.evm.mirasmanda.uz
Host
Chain ID
1215655279
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-11-16T20:22:35.621313184Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
688ms
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 'https://rpc-uat.evm.mirasmanda.uz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:26:51.418Z
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.