TorZon Market — questions & answers

TorZon Market topic hub. Anti-DDoS access queue, four-onion rotation, BTC and XMR settlement, English-language UI.

TorZon Market onion endpoints — verified set

Current v3 onion endpoints for TorZon Market. Verify the full 56-character fingerprint against the operator’s PGP-signed announcement on Dread before logging in. Click any address to open in Tor.

TorZon has been on Tor since 2022, which makes it one of the older English-language markets we cover. The interface is plain. Categories on the left, search at the top, vendor pages with the usual deal-count and dispute-ratio headers above the fold. No exotic UX experiments. If you've used Nexus or Mars, TorZon will feel immediately familiar.

The thing TorZon is actually known for is the queue. Every visit hits a server-side anti-DDoS waiting room first — a static "TorZon Access Queue" page that holds you for anywhere between a few seconds and a minute, depending on current load. It's a flood-control mechanism: bots that don't respect the queue can't hammer the login captcha. Annoying the first time, normal by the third.

Settlement is BTC and XMR. Monero is the default and the right choice if privacy is the reason you're on Tor at all. Bitcoin sits there for vendors who only take BTC. Deposit addresses are fresh per request, never reused. Withdrawal PIN is enforced separately from the login password — if someone steals your session cookie they still can't empty the balance without the PIN.

Mirror set is four v3 onions running concurrently — deeper than most operators. The current rotation is on the TorZon answer pages in this hub. Updates are posted as detached-PGP-signed messages on the operator's Dread account. Import the public key once and you can verify every announcement after. An onion in a Telegram channel that the operator didn't sign is a phishing attempt.

What are the TorZon Market onion addresses?

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:

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.

See also

Which cryptocurrencies does TorZon Market accept?

TorZon Market settles in Bitcoin and Monero. No Litecoin, no Ethereum — the operator stuck with the standard 2026 pair.

BTC XMR

Notes per currency

Monero (XMR). The default privacy option and what TorZon expects you to use. Sender, receiver and amount are hidden at the protocol layer. If you do not have a strong reason to use Bitcoin, pick this one.

Bitcoin (BTC). Widely accepted and easy to source, but the trade-off is transparency — the BTC ledger is fully public and forensic services routinely correlate exchange withdrawals with on-chain darknet activity. Use BTC only when the vendor does not offer XMR.

Deposit flow

Deposit addresses are generated fresh per request and never reused. After the configured number of on-chain confirmations the funds credit your account balance. Withdrawals follow the same fresh-address pattern and require a separate PIN that is not the login password.

See also

What is the TorZon access queue and why does every visit start with a waiting page?

Every visit to a TorZon onion first hits a server-side waiting room — a plain static page titled TorZon Access Queue. It holds the request for anywhere between a few seconds and roughly a minute, then forwards you to the actual marketplace. The hold time varies by current load.

Why it exists

A single hidden service is cheap to flood. If the operator put the login captcha directly behind the onion, a bot pool could hammer it indefinitely and either knock the marketplace offline or burn through every Tor circuit available. The queue absorbs that traffic before it reaches the application layer: bots that do not respect the wait drop off, real users wait briefly and continue.

What it looks like

A near-empty HTML page (~26 KB) with the TorZon favicon embedded inline and no other resources. No JavaScript challenge, no captcha — just a fixed delay enforced server-side. When the queue releases your session, the marketplace homepage loads on the next request.

Phishing signal

A clone of TorZon that serves the marketplace UI without the access queue is almost certainly a phishing front-end. The queue is part of the operator’s stack and cannot be cheaply replicated by a clone that just scrapes screenshots. If the page you land on skips the wait, close the tab and re-check the onion against the operator’s PGP-signed mirror list.

See also

Background reading