https://rpc1.testnet.camdl.gov.kh/

CamDL Testnetevm

gov.kh· rpc1.testnet.camdl compare ↔● fastest right now

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_256_GCM_SHA384

KEX group

classical

PQ class

Classical only

ALPN

Cert expires in

26d

Session resumed

yes

TLS handshake

298ms

Resumption

283ms

TTFB

1.38s

RPC block height

23,096,149

TLS handshake

VersionTLS 1.3

CipherTLS_AES_256_GCM_SHA384

KEX groupclassical

ALPNh2

PQ classClassical only

Handshake298ms

Resumed?yes · 283ms

OCSP stapledno

SCTs presentno

Certificate chain

Subjectrpc1.testnet.camdl.gov.kh

IssuerYR2

Key typeRSA-2048

Chain length3

SANsrpc1.testnet.camdl.gov.kh

Not before2026-08-05

Not after2026-11-03

Days to expiry26d

Chain SHA-25644ca65167b263f69…

Misconfigurations

OCSP stapling not enabled no_ocsp_staple

Grades

Posture

B83

Speed

F58

Certificate

100

TLS profile

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc1.testnet.camdl.gov.kh/

Host

rpc1.testnet.camdl.gov.kh

Chain

CamDL Testnet

Chain ID

395

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

Classical only

Key exchange

Cipher

TLS_AES_256_GCM_SHA384

Last seen

2026-10-07T23:57:49.429541819Z

History (30 days)

no history

Chain peer ranking

This URL is fastest right now

YES

Fastest p50 latency

1.38s

Latest block height

Current fastest URL

https://rpc1.testnet.camdl.gov.kh/

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

Scan reportschema rpcscan-report · captured 2026-10-10T08:27:59.233Z

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.