Live Nexus Market Onion Mirrors

Mirror Tier Definitions

Public mirrors are addresses published by the operator in PGP-signed Dread posts. Each public mirror has a verifiable signature trail back to the operator pinned key. We refresh the public mirror list against the latest signed post within twenty-four hours of any rotation announcement.

Leaked mirrors are addresses that originated inside private channels (vendor-only handouts, beta-tester pools) and surfaced in closed chats before becoming widely known. They still route to the real Nexus back-end but the operator has not endorsed them publicly. We list them as fallback because they work today; we cannot guarantee they will work tomorrow.

Rotation Mechanics

When the operator retires a mirror, the dead onion stops resolving within hours. There is no redirect, no replacement banner inside the dead onion, nothing announcing the rotation on the retired address. Stale bookmarks pointing at retired mirrors return destination-unreachable errors.

The new address shows up as a fresh PGP-signed Dread post. The pinned operator key signs the post; the addresses inside become canonical. Within twenty-four hours of the post, this page is updated and the rotation propagates through the mirror tracking infrastructure.

Verification Procedure

Three independent checks confirm a mirror onion is authentic Nexus and not a phishing clone:

1. Character-by-character comparison of the 56-character v3 address against the operator PGP-signed Dread post.
2. Comparison of the canonical onion printed inside the marketplace banner against the URL bar after the page loads.
3. Verification of the fingerprint embedded in the login captcha image against the URL bar address.

All three checks must pass before any credentials are typed. Any single failure indicates a phishing copy and the tab should be closed immediately.

Mirror Status Tracking

Our probe array pings every tracked mirror every fifteen minutes from independent Tor circuits. Response time, HTTP status, and TLS handshake outcome are recorded. A mirror that fails three consecutive probes is flagged for review; sustained failure for twenty-four hours triggers a status downgrade on this index.

The rolling thirty-day uptime number on each mirror card averages those probe results, weighted toward recent measurements. Brief blips of a few minutes do not significantly affect the displayed number; a prolonged outage does. The probe schedule itself rotates across our circuits to avoid creating an identifiable traffic pattern.

What Mirror Failure Modes Look Like

Three failure modes account for nearly all observed Nexus mirror outages. The most common is denial-of-service overload, where the mirror is reachable but response time exceeds thirty seconds; the marketplace responds but slowly enough that users assume it is down. The second is descriptor expiry from the Tor directory cache without a fresh announcement, where the mirror onion stops resolving entirely. The third is operator-initiated retirement, where the mirror is deliberately taken offline and a replacement appears in a signed Dread post.