TorZon Market currently runs four v3 hidden-service endpoints concurrently. That is a deeper mirror pool than most operators here. The current set, verified against the operator’s most recent PGP-signed Dread post, is:
- 01 torzon4v7bcakvo7qikdfknewj4dlr44hkyv4jyfrkl7ci3zqn76kiid.onion
- 02 ncmebasolcj2pmw5oy2bco4r65jbcqznrujtxcalz6e2b2jmhjlf44ad.onion
- 03 otw35cxf2rssl23tsvtqjwj32u62q4becl2jmgvekuemptxli7gt5lyd.onion
- 04 dgkozv5myc3lfpedjl2khhk6icok2xm5wmc5vg42xvbyh4fs345mopyd.onion
All four resolve to the same back-end. Use whichever one your Tor circuit reaches first — same account, same balance, same orders. If an address slows down, paste the next one from the list above into Tor Browser and continue.
About the access queue
Every onion above first lands on an anti-DDoS waiting room — a static "TorZon Access Queue" page that holds the request for a few seconds to a minute depending on current load. That is by design: the queue absorbs flood traffic before it reaches the login captcha. The market itself loads as soon as the queue lets the request through. If a clone serves you the marketplace directly with no queue, treat that as a phishing signal.
How the rotation works
The operator does not retire onions silently. When an address is added or removed, the change ships as a detached-PGP-signed announcement on the operator’s Dread account, with a date stamp. The set above was current at the last sync — glance at the Dread post once before submitting credentials to make sure nothing has rotated. See how to verify a Tor market onion address for the verification workflow.