Geographic redundancy
Mirrors are not clustered in one place, so a regional disruption does not take the whole service down — traffic shifts to entries that are still healthy and the Torzon onion stays reachable.
Every Torzon onion mirror in the list below is checked against the operators' PGP-signed announcement before it appears, and each status pill reflects a live probe — never a hard-coded "online" label. Copy a verified address, open it in Tor Browser at the Safest level, and confirm the signature before you log in. The address proves nothing on its own; the signature over it proves everything. Verify first.
Below is the current set of Torzon onion mirrors. Each row carries the full v3 address with user-select:all so a single tap selects the whole string, a Copy button, and a status that comes from a live check rather than a label typed by hand. Torzon runs 9+ mirror onion URLs with regular rotation, so this table is the live picture, not a snapshot frozen at publish time.
To open the live, verified Torzon onion mirror list, arrive through a search engine result (Bing, DuckDuckGo, Google) or start from the official Torzon onion on our homepage. This referer check keeps scraped clone lists from harvesting fresh addresses. The verified onion box on the homepage is always available.
How should you read this list? Three habits keep you on the genuine Torzon onion:
The whole point of a multi-mirror setup is that no single Torzon onion URL is a point of failure. If one address is slow or cycling out, another verified mirror carries the same marketplace. That redundancy is why the list matters more than any one link. A working mirror is more than a string that resolves, though — the address has to carry a valid PGP signature, the warrant canary has to be current within 72 hours, and the status pill has to come from a live probe. When all three line up, the mirror is one you can connect to with confidence. When any one is missing, the right move is to pick another row or fall back to verifying by signature directly.
It helps to understand what sits behind the list, because the design explains why the marketplace stays reachable even when individual addresses come and go. Torzon spreads its service across geographically redundant infrastructure with load balancing across mirrors, multi-level protection against traffic floods, and a memory-resident backend that writes little to disk. The mirror addresses are the visible front of that system; the resilience is in how they are distributed.
Mirrors are not clustered in one place, so a regional disruption does not take the whole service down — traffic shifts to entries that are still healthy and the Torzon onion stays reachable.
Requests spread across the fleet rather than piling onto one address, which keeps any single mirror from buckling under demand and smooths out the slow loads users notice most.
Multi-level filtering blunts denial-of-service attacks, and because the surface is split across many addresses, an attack on one does little to the rest.
None of this is something you configure. It is the reason the list keeps producing a working entry even after the address you used last week has rotated out. The infrastructure does the heavy lifting; your job is only to verify the address you land on. Pair that with the platform's broader security model — PGP, layered 2FA, post-quantum encryption, and the 72-hour warrant canary — and a verified Torzon onion mirror is a well-defended door, not a fragile one.
A Torzon onion mirror is only as trustworthy as the signature behind it. Anyone can register a string that looks close to the real address; nobody but the operators can sign the correct one with their PGP key. That asymmetry is the entire verification model, and it is the reason a verified Torzon onion beats a "found it on a forum" address every time.
.onion. Anything shorter or with stray characters is fake on its face.Three signs mark a fake Torzon onion mirror. The signature fails or is missing. The address is the wrong length or uses characters Base32 never contains. The warrant canary is stale or its signature has changed. Any one of those means stop. A clone copies the look of the marketplace; it cannot copy a valid signature over the right address. For a step-by-step walkthrough with screenshots, the full Tor and PGP guide on the info page covers how to open the Torzon onion in Tor from a clean install.
Reaching a Torzon onion mirror takes four steps in Tor Browser. Do them in order — the security level in particular is what keeps the session private.
torproject.org site only, and set it up before pasting any address.Onion connections take a few seconds longer than clearnet because Tor negotiates a rendezvous circuit before the page loads. That short wait is normal. If a mirror does not load on the first try, build a new Tor circuit for the site and reload — that single step clears most failed onion loads — or switch to another verified Torzon onion mirror from the table above.
New visitors often ask why the Torzon onion address they saved last month no longer works. The answer is by design: URLs rotate for resilience. Rotation is a defense, not a glitch, and understanding it changes how you should bookmark. Two pressures drive rotation. The first is DDoS — onion services are targets for traffic floods, and spreading the marketplace across 9+ mirror addresses means an attack on one URL does not take down the whole service. The second is resilience against tracking — rotating addresses on a schedule makes it harder for any observer to pin a single long-lived endpoint, which fits the platform's RAM-only, log-light posture.
The practical consequences for you are short:
This is also why a static list found elsewhere goes stale fast while a maintained, signed list stays useful. Rotation breaks anything frozen in place. The Torzon onion mirrors here are refreshed against the signed announcement so the table tracks the rotation instead of falling behind it.
Status and uptime are different questions, and both matter when you pick a Torzon onion mirror. Status is now — is this specific address responding this cycle? Uptime is the track record — how reliable is the service over months?
On status: each pill in the mirror table comes from a live probe. "Online" means the address answered the most recent check; "checking" means it has not confirmed this cycle and you should pick another or verify by signature. There is no hard-coded "online" anywhere here, because a fake status is worse than no status — it invites you to trust a mirror that may have rotated out.
On uptime, the record is strong. Torzon held 98%+ uptime across 2026, with downtime averaging under four hours a month, and verified mirrors have run near 99.7% availability as a fleet. That reliability is a direct product of the multi-mirror design: when one Torzon onion URL is rotating or under load, others carry the traffic, so the marketplace as a whole rarely goes dark. If a single mirror is slow, that is a mirror problem, not a marketplace problem — switch addresses and you are back on. The list exists precisely so a single slow Torzon onion never means the door is closed.
Verify the PGP signature. Import the operators' public key, check that the signed mirror list reports a good signature, then match the address character for character — all 56. Confirm the length and Base32 format and that the warrant canary is current. A clone can copy the page but never a valid signature over the correct address.
It almost certainly rotated. Torzon runs 9+ mirrors and cycles URLs on a schedule for DDoS resilience and tracking resistance. Pull a current address from the live table above rather than assuming the service is down, and in future bookmark the signed source instead of a raw address.
There are 9+ mirror onion URLs in rotation. As a fleet they have run near 99.7% availability, on top of the platform's 98%+ uptime across 2026 and under four hours of downtime a month. The redundancy means one slow mirror rarely affects access overall.
First rebuild your Tor circuit and reload, since a stale circuit can make live addresses look unreachable. Give each onion connection 10–20 seconds to negotiate. If the status genuinely has not refreshed, verify a listed address by its PGP signature and connect once it matches — a good signature is authority even before the probe catches up.
Copy any verified mirror above, set Tor Browser to Safest, and you are on the marketplace in one move. Want the canonical entry point? Head back to the official Torzon onion on the home page, where the primary v3 address sits in the hero with a live status. New to Tor, or hitting errors? The full guide on the info page walks through installation, PGP verification, and circuit fixes from scratch.