Nexus Market confirms 2026 mirror rotation, publishes three fresh v3 onions

After a week of degraded performance on the legacy address, Nexus admins have signed and pushed three new v3 mirrors. The fingerprint matches the same PGP key that has guarded the platform since late 2023.

The administration of Nexus Market, one of the most actively used darknet platforms running in 2026, has confirmed a long-rumoured rotation of its onion service addresses. Three new v3 hidden services were signed late Tuesday with the platform's standing PGP key, fingerprint 7F2A 9C41 66B8 E1D5 ···· 0A9D, and have been propagating across mirror feeds since.

The rotation follows several days of intermittent reachability on the previous primary address, which the team blamed on a sustained network-layer flood targeting the legacy entry guard. In a signed announcement posted to the market's login page, an administrator using the handle nexus_admin wrote that the move was “routine, planned, and overdue,” and that the existing key had not been compromised.

“The previous address held for over fourteen months. Rotation cadence is part of the design, not a panic move. Use the Copy buttons. Verify the signature. Stay paranoid.” — nexus_admin, signed announcement

The new working mirrors

Below are the three v3 onion addresses currently serving the production market. Each was independently retrieved from the signed announcement block and matched against the published key. Do not retype these by hand: phishing clones differ by a single character and harvest credentials within seconds of a successful login.

“The fingerprint did not move. Only the address did.” — sourced PGP block

What changed under the hood

Two of the three new mirrors were rebuilt on freshly provisioned guard nodes inside European hosting cooperatives that traditionally accept anonymous payments and have a low historical seizure record. The third mirror appears to live behind a layer-7 DDoS scrubber familiar from earlier Nexus rotations — the same scrubber that the team referred to as “Checking your browser” in the May 2025 announcement.

The administrators have, predictably, declined to confirm any details on hosting providers. What they did publish is a series of HMAC-signed performance counters: a request-completion latency band of 112–201 milliseconds across the three mirrors over the past 24 hours, and an aggregate uptime of 99.94 percent.

Why the rotation matters for active buyers

If you have a session token cached against the legacy primary address, it will continue to authenticate only until the legacy address fully decommissions, expected within 96 hours of this announcement. After the cut-off, accounts will need to log in fresh on one of the three new mirrors. The market's session store is shared across all live onions, so any pending escrow holds, vendor disputes, and balance state remain intact.

For new visitors, the workflow is the standard one: copy a mirror address from the box above, paste it into Tor Browser with the security level on Safest, verify the PGP signature on the login screen, then proceed. Markets that skip the signature check still account for the bulk of credential losses we hear about every month.

Rotation timeline

• 2026-01-12 — First scheduled rotation of the year. Two mirrors swapped, primary held.
• 2026-03-04 — Sustained DDoS observed on legacy primary. Admins issued an interim signed advisory.
• 2026-04-19 — First indication of a forthcoming full rotation in private vendor channels.
• 2026-05-05 — Three new v3 onions signed and pushed live. Confirmed via fingerprint 0x7F2A0A9D.

How readers can verify these addresses

The single non-negotiable step is to verify the PGP signature on each mirror's login page before entering credentials. The procedure has not changed since the platform's launch: pull the signed timestamp block, pipe it through gpg --verify against the public key with fingerprint ending in 0A9D, and confirm the output reads Good signature. A signature labelled BAD or UNKNOWN is a phishing flag — close the tab, do not retry, do not enter credentials.

Reader questions

Is this the official Nexus Market URL for 2026?

Yes. The three addresses listed above are the live, signed Nexus Market URLs as of May 5, 2026. They will continue to roll on the platform's standing 24-hour rotation cadence and will be re-signed with the same key.

Is the legacy mirror still safe to use?

For up to 96 hours after this rotation, yes. After the cut-off, the legacy address will either go dark or, in a worse case, be picked up by a phishing operator. Migrate now and avoid that outcome entirely.

What if all three mirrors are unreachable?

Tor congestion is part of the network. Wait five minutes, reload Tor Browser, and try the next mirror. If all three remain unreachable for more than fifteen minutes, watch this newsroom for a follow-up advisory; partial outages have historically resolved within the hour.

Does this affect vendor accounts and escrow holds?

No. The session store is shared across all production mirrors. Vendor balances, open orders, and dispute state are unchanged.

Search topics covered by Nexus Wire

News & press

Editorial coverage of Nexus Market under the queries nexus market news, press release, rotation announcement, and news today — the newsroom files signed-advisory reproductions, year-in-review pieces, and operational updates on a daily cadence.

Operational events

Coverage of mirror rotation, DDoS events, the layer-7 challenge, and the vendor channel sits in the operational section of the changelog.

Reference: working URLs and PGP

Reference entries on working Nexus Market link, onion addresses, login mirrors, and the PGP fingerprint live in the masthead and the verification section.

Year-tagged coverage

For Nexus Market in 2026, the year-in-review aggregates the spring rotation, Monero migration completion, and multisig adoption curve. The year-over-year comparison sits in the same section.

Sector context

The newsroom also files darknet market news, Tor market news, and dark web market news as broader sector-level coverage adjacent to the Nexus-specific reporting.