Nexus market mirrors, as published on this site
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionPublished as supplied. This site does not probe an onion, so nothing here is a claim that a given address opens for you right now.
A password manager note is a free text box beside a login. Readers use it for a v3 onion because the url field on most vaults expects a clearweb form and refuses a string that ends in .onion. The note field takes anything.
What it is
A password manager entry has a title, a username field, a password field, a url field and a note field. The url field validates. The note field does not. The nexus market login line, meaning the address the reader opens to reach the login page, sits in the note field on most vaults for the simple reason that the url field will not accept it or will not open it in the right browser.
The note travels with the vault. It syncs to every device the vault is on. It sits under the same passphrase the vault is under. When the vault is locked, the note is locked. When the vault is open, the note is open on every device the vault is open on.
Lifeline
- Only in the browser bar
- Inside a locked vault
- Copied out or vault rotated
What the note keeps
- The exact bytes of the string, because a note field is a plain text buffer and does not apply an autolinker until the entry is opened for viewing.
- The link between the string and the credentials, because the entry that holds the note is the entry that holds the passphrase and the username the reader uses on the market.
- The encryption at rest that the vault applies to every field it stores, so a disk that leaks the vault file does not leak the string in plaintext.
- The sync across the devices the vault is on, so the reader does not have to retype the string on a second device.
What the note loses
- The ability to jump to the address in one click, because most vaults do not treat the note as clickable and the url field on the same entry is a different field.
- The ability to survive a vault lock at the wrong moment, since a locked vault means an unreachable string until the passphrase is entered.
- The ability to find the string by a partial search that includes a hyphen or a slash, because most vaults do a literal substring search on notes and a typo in the note is a typo in the search too.
- The ability to travel outside the vault ecosystem, because the note is not exportable in a shape that another app parses.
The url field versus the note field
The url field on a password vault is designed for a clearweb login. It expects a scheme and a domain. Feed it a string that ends in .onion and it may reject it, may store it and refuse to open it, or may open it in the default browser rather than in the tor browser the reader was actually going to use. None of those are what the reader wanted.
The note field takes anything. Readers who care about this either keep the string in the note and open it manually, or keep the string in both fields and only ever click on the note. That second option is a duplication and the reader has to remember to rotate both when the string on the site above rotates.
What a search inside the vault will find
A vault search is literal. It matches a substring of the note. That means a reader who wrote "nexus market login" as the title finds the entry by typing nexus, market or login, but the string in the note itself is only findable by its first few characters, which are the same across the three mirrors on this site. A reader who typed the vanity prefix into the search sees all three entries at once and has to pick.