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.
The text is all there but the layout has collapsed and nothing clicks. It looks alarming and is usually the dullest possible cause.
The ordinary explanation
The document arrived and the stylesheet or script did not. On a thin circuit that is common, because the extra files queue behind the page and some of them time out. What you are looking at is a partial delivery rather than a different page.
How to tell it apart from something worse
- Check the address bar. A broken render at the correct onion is a delivery problem. A broken render at an address you do not recognise is a different conversation entirely.
- Reload once. A delivery problem usually fixes itself because the missing files are now closer to hand.
- If the page comes back complete on a second load, that was it. Nothing else to investigate.
When the security level is the cause
On the strictest browser setting some scripts do not run at all, which can leave controls dead by design rather than by accident. That is a fair trade and worth keeping. If a page genuinely cannot work without scripts and you need it, decide deliberately rather than dropping the setting out of habit.
What not to conclude
An ugly page is not evidence of a clone. Clones generally look better than the real thing, because copying a stylesheet is trivial and they want you comfortable. Appearance is not the test. The address is.
How to read the result
Assets timed out. Ordinary and finished.
Thin circuit or the mirror is shedding static files. New circuit, then another mirror.
Ignore the layout. Close the tab.
Other integrity signals
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 protection gate never lets you through
Anti flood gates on a Nexus mirror can loop forever. What causes the loop, why hammering makes it permanent and how to get past it.
IntegrityLogged out on every page you open
Constant logouts on a Nexus mirror are almost never the market. Where the session is actually being lost and what to check first.
Procedures that apply here
Requesting a new circuit, and when it actually helps
The single most useful control in Tor Browser for onion problems, what it does, what it costs and which symptoms it fixes.
SafetyConfirming you are on a real Nexus mirror
The check that separates the market from a convincing copy, why appearance proves nothing and what to do if the check fails.
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.