Links
Official Torzon onion links & mirror verifier
Page intent: copy published v3 hosts, run the paste-in checker against our JSON index, read fraud guidance — not market history or wallet rules.
Published Torzon onion mirrors
Daily reconcile (NY) · automated probe every 3.5h · reviewed 2026-10-12
Hostname rows unlock after 21+. The verifier below works without that step.
| Label | v3 hostname | |
|---|---|---|
| Primary | — | |
| Mirror 2 | — | |
| Mirror 3 | — |
Drug use is harmful to your health. Torzon Market Directory does not encourage purchasing controlled substances.
Directory link verifier
Paste a v3 hostname. Verified means the string matches one of the three hosts in data/mirrors.json — text match only, no live Tor ping from this site.
Mirror row labels
Primary, Secondary, and Tertiary are editorial copy order — not speed tests, uptime scores, or “more official” tiers. Any row that verifies against data/mirrors.json is a published host. If one label is slow during DDoS, try the next row in the table before you paste an unlisted URL from chat.
We never add a fourth “VIP” or “backup” onion on this domain. Extra hosts in ads are outside our index until operator-signed reconciliation adds them to the trio.
What the verifier does and does not do
- Does — compare your paste character-for-character to the three strings in our JSON index.
- Does not — connect to Tor, ping hidden services, or prove a host is online right now.
- Does not — replace PGP 2FA, anti-phishing phrase checks, or withdrawal PIN hygiene after login.
- Unknown result — means we do not publish that string; it is not a verdict that the onion is malicious or benign.
Run the checker on every surprise paste — forum signatures, QR codes, “support” links — before Tor Browser loads the host. UI walkthrough: Access.
Before you type credentials
Hostname verification starts on this page — paste-in checker and the published trio. Step-by-step gates, the anti-phishing CAPTCHA reference capture, and the manual checklist now live on Access so Links stays focused on mirrors and fraud patterns.
21+ copy gate (this page)
Full v3 strings and copy buttons require one-time age confirmation stored in this browser. The verifier, fraud prose, and eight hostname checks remain readable without unlocking copy — we gate clipboard access, not education.
Clearing site data resets the gate. Parent devices should not share an unlocked browser profile with minors.
Eight checks before you paste credentials
- Exact address — all 56 characters before
.onionmatch this directory table. - Real Tor Browser — current install from the official Tor Project bundle, not a clear-web “gateway” login.
- Onion lock — session stays on the v3 host; unexpected jumps to HTTP login pages are a stop sign.
- Sane login flow — expect DDoS gate, CAPTCHA, then username/password and 2FA — not email-verify traps.
- Signed mirror text — reconcile rotations with operator-signed announcements when hosts change.
- Your chosen source — not a DM or ad; you copied from this directory or a bookmark made after verification.
- Anti-phishing phrase — your personal words appear on every authenticated page on the real market.
- Withdrawal PIN — separate from login password; set only on the verified onion.
Why unofficial mirror lists fail
Credential theft
Clone sites harvest usernames, passwords, PGP responses, and mnemonics. One wrong character in the v3 body sends you to a different hidden service.
Wallet fraud
Fake support links push malicious deposit addresses or “verification” payments. Escrow UI can be simulated while funds never reach the real backend.
Stale mirrors
Republished old v3 hosts after rotations or mixed private rotator URLs. A fast load is not a signature.
Logged-in users may see an in-market Links Rotator during DDoS — those URLs must still match signed mirror text and this directory table before you trust them. See Policy for how we update the trio.
After a rotation, update Tor Browser bookmarks and re-run the verifier on any saved host. Phishing campaigns spike in the hours after legitimate mirror changes — treat urgency in DMs as suspicious.
When mirrors change
Operators publish new v3 hosts after sustained DDoS or infrastructure moves. We update the trio only after signed mirror reconciliation; the 3.5-hour probe loop flags rows that no longer align with published JSON.
Retire bookmarks that fail the verifier even if they worked last week. If two rows in our table load but a paste from Telegram does not, trust the table — not the chat screenshot.
During heavy DDoS, logged-in users may see an in-market Links Rotator. Treat those URLs like any other paste: run the verifier here, compare signed operator text, then follow the Access checklist before login.
Copy discipline
- Use buttons — copy controls after 21+ reduce typos in the 56-character body.
- One host per session — pick a row, load it, verify phrase; do not hop between unlisted onions mid-login.
- Verifier first on surprises — anything from forums, ads, or “support” gets pasted into the checker before Tor Browser opens it.
- JSON is source —
data/mirrors.jsondrives the table and checker; cached HTML alone is not enough after a rotation.
Links — short answers
What does Verified mean in the checker?
Exact match to one of three strings in our JSON index. Unknown mirror means no match — not proof the host is offline, only that we do not publish it.
Is Primary faster or safer?
Labels are copy order only. Pick a row that loads, keep the URL bar on that exact string, and confirm your phrase after PGP 2FA.