Every Torzon onion address tracked by the directory sweep. Status tags reflect the most recent probe. The rotator endpoint sits at the bottom of the page, plus the offline-verification manifest path.
/status.json exposedFunctionally, any of them. They all hit the same backend, the same account database, the same vendor catalog. Practically the answer depends on your Tor circuit at the moment of the request. The first one in the list is not necessarily the fastest from where you sit, since the order is sweep position rather than latency rank.
If you bookmark one and find it slow on a given day, rotate to the second or third. Tor circuits change frequently and a hop that was painful at noon may be perfectly snappy by evening.
A single bookmarked mirror is unreachable some fraction of the time. Three reasons drive that: stale v3 descriptors that have not republished yet, brief DDoS pressure on an introduction point, and the occasional planned rotation by Torzon staff. The rotator hides all three behind one address.
For users who would rather skip this page entirely, pull the signed manifest directly from the rotator at h3h66vql4ucodjre4bluwtywhoq2bjqxpgvxgv2xo2nkui5ney6gslqd.onion/manifest.txt.asc and verify the signature against the operator key. The fingerprint is published in the about page.
The error that costs people the most is pasting a mirror onion from a chat client that auto-shortens URLs. Always copy from the address bar after the page loads, never from a preview pill or a quoted message in a Telegram or Discord thread. Auto-shortened links may hide a character substitution that points you at a clone, and a clone collects credentials in real time.
The second most common error is typing an onion by hand. Do not. The address is 56 random base32 characters plus the suffix, and one wrong character resolves either to nothing or to a different hidden service entirely. Copy and paste only, every time.
The rotator does not log requests, store cookies, or send anything to a third party. The hidden service protocol does not even expose your IP to the operator, so there is nothing to log on that axis. The rotator also does not modify or proxy the Torzon traffic itself. After the 302, your browser holds a direct circuit to the mirror, and the rotator is out of the loop until the next request.