What is the TorZon access queue and why does every visit start with a waiting page?
Last reviewed: June 2026Every 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.