https://evm.qore.host

QoreChainevm

qore.host· evm 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

73d

Session resumed

yes

TLS handshake

74ms

Resumption

74ms

TTFB

835ms

RPC block height

3,872,242

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake74ms

Resumed?yes · 74ms

OCSP stapledno

SCTs (CT log)none in TLS ext

PQ strict?no (classical tolerated)

Certificate chain

Subjectqore.host

IssuerWE1

Key typeECDSA-P-256

Chain length3

SANsqore.host, *.qore.host

Not before2026-10-11

Not after2027-01-09

Days to expiry73d

Chain SHA-256127308a5b24cdc42…

Modern posture

HSTSno header

HTTP/3 (ALPN hint)no

ECH offeredno

DNSSECunsigned

CAA recordsnone published

Must-staplenot declared

Grades

Posture

A+95

Speed

C77

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Misconfigurations

OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL

https://evm.qore.host

Host

evm.qore.host

Chain

QoreChain

Chain ID

9801

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-28T09:49:34.373035708Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

YES

Fastest p50 latency

835ms

Latest block height

Current fastest URL

https://evm.qore.host

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

Scan reportschema rpcscan-report · captured 2026-10-28T11:19:17.580Z

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.