Torzon market mirror inventory
The full live onion list, plus the rotator endpoint. Reachable status is from the latest sweep, run every six minutes against each mirror.
Production mirrors (six)
Each mirror points at the same Torzon backend through a different hidden-service descriptor. They are interchangeable from the user perspective, you do not get a different account or different vendor catalog. Pick whichever is alive when you land.
Rotator endpoint
The rotator picks an online mirror on your behalf. The most reliable mode for a quick visit, since you do not need to know which mirror is currently fastest. Same operator key signs both the manifest and the rotator response.
Endpoints on the rotator onion:
/: 302 redirect to the lowest-latency live mirror/status.json: per-mirror reachability and last-check timestamps/manifest.txt.asc: PGP-signed flat list of mirrors, for scripts
How verification works on this page
The mirror inventory shown above is generated from the operator manifest. That manifest is an ASCII file, one onion per line, signed with the operator PGP key whose fingerprint is published on /security. If you want to skip this page entirely and pull from the source, fetch the manifest from the rotator endpoint and verify the signature locally.
The sweep that flags mirrors as reachable performs a simple HTTP GET / over Tor, checks for the expected response header, and records the round-trip latency. A mirror that fails three sweeps in a row drops off the list until the operator re-signs.
Common mistakes when copying mirrors
- Pasting from a chat client that auto-shortens URLs. Always copy from the address bar, never from a preview pill.
- Confusing similar-looking onions from clone phishing pages. The address always ends with
.onion, never.comor.shop. - Typing the onion by hand. Do not. Copy paste only.
- Pasting an onion into a clearnet browser. Tor Browser is required, regular Chrome or Firefox will not resolve a hidden service.
Picking a mirror by hand
If you prefer not to use the rotator, picking a mirror by hand is fine. The selection criteria most operators use, in order: which one resolves the fastest on your current circuit, which one returns a clean header response, and which one has not failed a recent sweep. The page above orders the list by sweep position, not by latency, so the first mirror in the list is not always the fastest from where you sit. Try the second or third if the first feels slow, sometimes a Tor circuit just lands awkwardly the first time.
If you want to bias toward stability over speed, the older mirrors at the top of the list have been in the manifest the longest and tend to have the fewest descriptor refreshes per week. Newer mirrors are added when the operator brings additional capacity online, usually after a sustained period of DDoS pressure on the existing set.
Mirror header check
When you land on a Torzon mirror, the first thing the homepage should return is a familiar login splash with the green status pill in the top right. If you instead get a 200 with a blank page, or a redirect to a different onion you did not pick, close the tab and re-pick from the list above. That behavior is the most common signal of a misconfigured proxy or an outright phishing copy in front of a real mirror, and credentials entered on that intermediate page never reach Torzon.