RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://xmr-node.cakewallet.com:18081

Moneromonero_rpccakewallet.com· xmr-nodecompare ↔● fastest right now● PQ hybrid
Posture score
76
Speed score
39
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
-
Cert expires in
72d
Session resumed
no
TLS handshake
310ms
Resumption
43ms
TTFB
2.26s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPN-
PQ classPQ hybrid
Handshake310ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectxmr-node.cakewallet.com
IssuerGoDaddy TLS Intermediate CA DV - R1v1
Key typeRSA-2048
Chain length4
SANsxmr-node.cakewallet.com, www.xmr-node.cakewallet.com
Not before2026-06-10
Not after2026-12-25
Days to expiry72d
Chain SHA-256ad29a77ce4c6f920…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C76
Speed
F39
Certificate
100
TLS profile
85
Post-quantum
90
RPC reachability
30
Misconfigurations
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple
Endpoint identity
URL
https://xmr-node.cakewallet.com:18081
Host
Chain
Chain ID
-
VM
monero_rpc
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_256_GCM_SHA384
Last seen
2026-10-14T12:14:47.57964847Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
2.26s
Latest block height
-
Using this RPCtabs auto-fill the URL
Generic JSON-RPC ping. Adjust the method to whatever the chain expects.
curl 'https://xmr-node.cakewallet.com:18081'
Scan reportschema rpcscan-report · captured 2026-10-16T00:43:01.230Z
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.