https://rpc1.camdl.gov.kh/
Posture score
83
Speed score
38
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
26d
Session resumed
yes
TLS handshake
423ms
Resumption
337ms
TTFB
2.38s
RPC block height
38,886,144
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake423ms
Resumed?yes · 337ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc1.camdl.gov.kh
IssuerYR2
Key typeRSA-2048
Chain length3
SANsrpc1.camdl.gov.kh
Not before2026-08-05
Not after2026-11-03
Days to expiry26d
Chain SHA-256e22631643b901ecb…
Misconfigurations
- OCSP stapling not enabled
no_ocsp_staple
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
Class
Classical only
Key exchange
-
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-07T23:57:37.372033546Z
History (30 days)
no history
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://rpc1.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-10T05:52:19.724Z
SHA-256 of canonical content
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.