nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionRun the check before you sign in. Open these in Tor Browser only. When the login screen loads, compare the onion printed on the page against your address bar, reading from the end. If they differ, close the tab.
A copy of the market can look perfect. It cannot live at the right address. That single fact is the whole of this procedure.
The check
- Copy an address from a place you already trust rather than typing or searching.
- Load it and stop at the login screen.
- Compare the onion printed on the page against your address bar, reading from the end backwards.
- Only then sign in.
Why reading backwards
The interesting characters are at the end. Anybody generating a lookalike spends their effort on a matching prefix, because that is what people glance at. The tail is expensive to match and is where a fake usually gives itself away.
What proves nothing
- The page looking right. Stylesheets are public to anybody who loads the site.
- A working login form. It works because it is collecting what you type.
- A padlock or the absence of one. Onion addresses carry their own authentication and browser warnings about certificates say nothing useful here.
- A search result ranking. Nothing about ranking is a statement of authenticity.
If it fails
Close the tab. Do not sign in to see what happens, do not send a test amount, do not report it from that page. Then change any password you reused elsewhere, because that reuse is where the real damage is.
The habit that prevents all of this
Keep the three addresses saved somewhere you can reach without a search engine. Every phishing story starts with a familiar address going quiet and somebody going looking.
Other procedures
What to do when none of the three answer
How to tell a service wide outage from a problem on your side, and the one action that turns an inconvenience into a loss.
MethodHow to take an honest reading of a mirror
A repeatable way to measure whether a Nexus mirror is slow, broken or fine, without tooling and without fooling yourself.
MethodChoosing which of the three mirrors to use
The three Nexus addresses reach the same market. How to pick between them sensibly and why the fastest one today may not be tomorrow.
Signals this procedure fixes
The address on the page is not the address in your bar
The one signal that ends a session rather than starting a diagnosis. How the check works on a Nexus mirror and why it cannot be faked.
IntegrityThe page loads but half of it is missing
Unstyled pages and dead buttons on a Nexus mirror usually mean the assets did not arrive, not that the page is a fake. How to tell the two apart quickly.
ReachabilityOnionsite Not Found
What the 0xF0 error means when a Nexus mirror will not open, why retrying rarely helps, and which of the three addresses to try next.