Independent · original reviews and scoring, sourced from each provider directly.v0.4
lesskyc

Safe Monero remote nodes

Public Monero nodes that are online, in sync and — where it can be checked — running the Monero Research Lab spy-node ban list. Re-tested from our own server every 30 minutes. Out of 428 nodes checked, 128 pass and 51 run the ban list.

Last reviewed · How we research · Suggest a correction

Best option: run your own node. A remote node can't steal your coins or see your balance, but it does see your IP address and when you send. If you use one, connect over Tor or I2P and pick a node with the ban list on.
Node addressBan listUptimeCountryOur check

Updated · list: xmr.ditatompel.com · re-checked by LessKYC

Check a node

Paste a node address or IP. We check it against this list and the MRL ban list in your browser — nothing is sent anywhere.

How to connect

Feather

Settings → Network → Node → choose “Custom” and paste the address. Feather can route everything over Tor (Settings → Network → Proxy).

Cake Wallet

Settings → Connection and sync → Manage nodes → add the node. For .onion nodes turn on Cake's built-in Tor first.

Monero GUI / CLI

GUI: Settings → Node → Remote node → add the address. CLI over Tor: monero-wallet-cli --proxy 127.0.0.1:9050 --daemon-address ADDRESS:PORT

Why the ban list matters

Researchers found large groups of “spy nodes” that log which IP address first broadcasts each transaction. The Monero Research Lab publishes a list of their IP ranges; nodes that load it (--ban-list) refuse to talk to them. Tor and I2P nodes hide their IP, so the ban-list status of most onion nodes can't be checked from outside — they show as “unknown”, which is normal.

Ban list in use: Monero Research Lab spy node ban list version 2, 2025-12-10 (431 entries). Raw data: nodes.json, banlist.json.