Skip to content
XMR Utility Network
PrivacyBeta

Privacy Protection Suite

Monero is private by default at the protocol level. Most leaks happen around it: networks, nodes, exchanges and habits. These tools and guides cover the parts you control.

Automated configuration checks

Public node check

Enter the address of YOUR public Monero node. Our server sends a few read-only RPC calls (get_info, and two methods a restricted node must refuse) and reports what anyone on the internet can see.

Only the URL is sent. No password, no key. We do not save it (only a 60-second in-memory cache); like any request it appears in Cloudflare's short-lived operational logs. Allowed: http/https, a DNS hostname (no IP addresses), ports 80, 443, 18081, 18089. Limit: 6 checks per minute. .onion and .i2p nodes cannot be reached from our servers. Use the offline config analyzer below for those.

Config analyzer (offline, in your browser)

Paste a monerod.conf, a monero-wallet-rpc config, or the command line you start them with. The analysis runs in this page only: the text is never sent, stored or logged.

Runs locally. Remove passwords before pasting anyway: you should never need to share them.

Site & service check

Is this the real Monero site, wallet download or service, or a look-alike? Paste the address before you download a wallet or enter anything. The answer comes from RugWard's live Monero site checker: a sourced list of official and known sites, look-alike and homoglyph detection, the PhishDestroy phishing feed, domain age, DNS and HTTPS.

Only the address is sent (to our server, then RugWard's checker). The site itself is never opened or downloaded; at most a HEAD request checks HTTPS. Nothing is stored.

No mixer

We do not run a mixer and never will: Monero's ring signatures, stealth addresses and RingCT already hide senders, receivers and amounts on-chain.

Guides

Honest limits

  • Nothing here makes anyone untraceable. We reduce leaks; we do not promise to remove them.
  • The node check sees only what the internet sees (from Cloudflare's network); it cannot reach .onion or .i2p nodes and cannot prove that no weakness exists. The config analyzer applies known rules to the text you paste and cannot see anything you did not paste.
  • The site & service check reports what RugWard's checker finds (sourced lists, look-alike rules, one phishing feed, DNS, HTTPS). A new phishing site may not be listed yet; "unknown" never means safe.
  • We never collect seeds or spend keys, and we do not store the txids you check (short in-memory cache only).