https://test.qrdx.org/rpc

QRDX Testnetevm

qrdx.org· test compare ↔● fastest right now● PQ hybrid

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

38d

Session resumed

yes

TLS handshake

166ms

Resumption

188ms

TTFB

1.52s

RPC block height

990,314

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake166ms

Resumed?yes · 188ms

OCSP stapledno

SCTs (CT log)none in TLS ext

PQ strict?no (classical tolerated)

Certificate chain

Subjectqrdx.org

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsqrdx.org, *.qrdx.org

Not before2026-08-25

Not after2026-11-23

Days to expiry38d

Chain SHA-256bbaf8d41378a5202…

Modern posture

HSTSno header

HTTP/3 (ALPN hint)advertised in HTTPS record

ECH offeredyes · encrypted ClientHello published

DNSSECunsigned

CAA recordsnone published

Must-staplenot declared

Grades

Posture

A+96

Speed

F55

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Misconfigurations

OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL

https://test.qrdx.org/rpc

Host

test.qrdx.org

Chain

QRDX Testnet

Chain ID

7620

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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-10-15T19:27:03.590993991Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

YES

Fastest p50 latency

1.52s

Latest block height

Current fastest URL

https://test.qrdx.org/rpc

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://test.qrdx.org/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-15T21:53:49.320Z

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.