5 verified addresses
Updated April 21, 2026PGP-signed from Dread
Torzon onion link 2026: all verified addresses
Five mirror addresses. Each sourced from Torzon's PGP-signed announcements on privacy-first communities. Copy the address below — never type it. One wrong character routes you to a phishing clone.
Every address below is sourced from Torzon's PGP-signed posts on Dread. No address is added without a valid cryptographic signature. Find an address elsewhere that doesn't match these exactly — it's not legitimate.
Avg. 0.31s response
Online
Loading...
Verified April 21, 2026 · PGP-signed · 99.1% uptime
Avg. 0.44s response
Online
Loading...
Verified April 21, 2026 · PGP-signed · 98.7% uptime
Avg. 0.68s response
Online
Loading...
Verified April 19, 2026 · PGP-signed · 97.4% uptime
Avg. 0.51s response
Online
Loading...
Verified April 21, 2026 · PGP-signed · 98.9% uptime
Avg. 0.47s response
Online
Loading...
Verified April 20, 2026 · PGP-signed · 98.3% uptime
Source protocol: All addresses are reconciled against Torzon's PGP-signed posts on Dread, twice daily. Last reconciliation: April 21, 2026. If any address fails to load in Tor Browser, try the next — all five connect to the same backend infrastructure. See the access tutorial for Tor setup and the security section for verification steps.
02Architecture
Mirror infrastructure: why Torzon runs five addresses
Five addresses. One market. And a reason every careful user bookmarks all of them.
The Torzon mirror infrastructure
Torzon operates five independent hidden service addresses, each running on geographically separated hardware. "Mirror" is something of a misnomer — these aren't read-only copies. All five connect to the same live database. When you register through Address 01 and log in through Address 03, your account, order history, and wallet state are identical on both. The differentiation is purely at the network layer: five distinct Tor hidden service keys, five different relay paths through the Tor network.
The architecture exists because of one specific threat: distributed denial-of-service attacks. A DDoS against a single .onion address floods the guard relays associated with that particular hidden service descriptor. With five addresses, an attacker would need to simultaneously overwhelm all five independent relay sets — an order-of-magnitude more expensive operation. Throughout 2024 and 2025, this design kept Torzon under 4 hours average downtime per month during periods when single-address markets faced days of complete unavailability. That's not a coincidence. It's the architecture working as intended.
How mirrors stay synchronized
The backend database is shared across all entry points. When you place an order through Address 02, the transaction record is immediately visible if you check through Address 04. This isn't database replication with propagation delays. It's a single database with multiple front-doors, each speaking through a different hidden service identity.
Torzon publishes all five addresses in a single PGP-signed message posted to Dread. The signature covers all five addresses simultaneously, meaning you verify the entire set against one key rather than authenticating each address separately. When an address is rotated — typically after repeated targeting in DDoS campaigns — the replacement appears in the next signed announcement. It's never added silently. Verification is the only path onto this directory. See GnuPG documentation for key import and signature verification steps.
"The five-mirror setup isn't a backup plan. It's the baseline. Markets running one address accept being one DDoS away from total unavailability."
Community analysis, Dread forum, January 2026
When to switch mirrors
In practice, most users never need to switch. The primary address resolves within seconds for the vast majority of connections. But three situations warrant switching. First: if the connection hangs beyond 30 seconds, try another — your Tor circuit may have picked slow relays for that hidden service. Second: during active DDoS events, Torzon's interface shows which mirrors are under pressure; use one that isn't. Third: in regions with heavy Tor censorship, different mirrors may have better relay paths available due to geographic variation in the Tor network.
All five addresses work identically for registration, purchases, and account management. Start with Address 01. If it's slow, fall back to any other. They're interchangeable. The only thing that changes is the route through the Tor network to reach the same destination.
03How to verify
Verification protocol: confirm any Torzon link before use
Phishing sites copy Torzon's exact design. The only way to know you're on the real market is to verify the .onion address character by character against a PGP-signed source.
Step 1: locate the official PGP announcement
Torzon's verified addresses are published as PGP-signed posts on Dread — the darknet forum accessible via Tor Browser. Find the Torzon subdread and look for posts with "verified mirrors" or "official link update" in the subject line. The post content contains a PGP-signed block with all five addresses.
Torzon's team uses a consistent PGP key — the same key since the 2022 launch. Its fingerprint is publicly associated with the Torzon brand on Dread. If a post claims to contain verified links but lacks a signature, or uses a different key fingerprint, treat it as suspect. An unsigned list of addresses proves nothing.
Step 2: verify the signature
Copy the entire signed block — from -----BEGIN PGP SIGNED MESSAGE----- to -----END PGP SIGNATURE----- — into a text file. Then run:
gpg --verify signed-torzon-message.txt
A successful verification returns Good signature from "Torzon Team" with the correct key fingerprint. BAD signature or a different fingerprint means the message was tampered with — don't use any addresses from it. GnuPG is free and included in Tails OS by default. On Windows, Kleopatra provides a GUI alternative.
Step 3: compare against known-good sources
After verifying the PGP signature, compare the addresses in the signed message against what's listed here. Both should be identical. If they differ — either Torzon rotated an address (the Dread post will explain), or one source has been compromised. Cross-reference against at least two independent verified sources. One confirmed match isn't enough. Three is.
Store verified addresses in KeePassXC. The autofill feature works only on the exact stored URL — it won't autofill on a phishing site with a different address, even if the page looks identical. That alone stops most phishing attempts mechanically, without requiring visual comparison. For OS-level protection, Whonix and Qubes OS both reduce the attack surface further.
The character trap: how phishing works
Torzon's verified addresses are 56 characters long. Phishing sites substitute one or two characters — typically in the middle where the eye naturally skips. The modified address resolves to a completely different hidden service controlled by the attacker, but displays a pixel-for-pixel copy of Torzon's login screen.
Torzon's built-in anti-phishing code: a personal phrase set during registration, visible before every login. A phishing clone won't know your phrase.
The primary address ends in ...yvqjqvvvomaw3hmjuid. A phishing version might end in ...yvqjqvvvomaW3hmjuid — one uppercase W substituted for lowercase. Or a digit swapped for a similar-looking letter. A 56-character string is impossible to verify visually at speed. Copy, don't type. And after reaching the real site, set your anti-phishing code in account settings. The phrase appears on every legitimate login page. A clone won't show it.
The EFF has documented extensively why darknet market users face disproportionate phishing risk. The combination of irregular browsing habits, high-value targets, and willingness to use unverified links makes this community a persistent focus of credential-harvesting operations. The countermeasures are simple. Using them consistently is the entire challenge.
04Reliability data
Mirror reliability report: January–April 2026
Historical uptime data collected from community monitoring across the first quarter of 2026. All five mirrors showed availability above 97%.
Mirror status — April 21, 2026
All 5 mirrors online
Mirror
Status
Uptime %
Avg. response
Last incident
Address 01
● Online
99.1%
0.31s
Mar 11 — 47 min
Address 02
● Online
98.7%
0.44s
Feb 28 — 23 min
Address 03
● Online
97.4%
0.68s
Apr 3 — 2h 18m
Address 04
● Online
98.9%
0.51s
Jan 15 — 35 min
Uptime calculated over the January–April 2026 monitoring window. Address 05 was added in March 2026 and lacks a comparable baseline — omitted from this table. Market story page has historical context from launch through 2025.
The April 3rd event on Address 03 — 2 hours and 18 minutes — was the longest recorded incident in 2026 so far. It coincided with a coordinated DDoS campaign targeting multiple major darknet markets simultaneously. All four remaining Torzon addresses stayed online throughout. Users who had bookmarked any other address were entirely unaffected. The event demonstrates why the five-mirror design isn't over-engineering.
Address 01 combines the best uptime and fastest response time across the monitoring period, making it the most reliable starting point. The January 15th incident on Address 04 was self-induced — a maintenance window that ran slightly longer than planned. Not a security event. For users in regions with variable Tor performance, Address 04 and Address 02 show consistent sub-0.5s response times that hold well under load.
Torzon's internal mirror status panel — response times and live availability across all active addresses.
05Reader questions
Questions about Torzon links, answered
Five questions readers ask most often. Specific answers only — no generic advice. For the full setup guide, see the access tutorial.
01
What does it mean when Torzon says a mirror is "down"?
A "down" mirror means the Tor hidden service for that specific address is temporarily not responding. The most common cause is DDoS attacks targeting that hidden service descriptor's guard relays — not a compromise of the market itself. The other four mirrors continue independently. None of the underlying data is affected. Torzon averages under 4 hours total downtime per month across all mirrors combined, and individual incidents typically resolve within an hour. If a mirror goes unresponsive, switching to any other address brings you to the same functional market with the same account state. Works every time.
02
Is it safe to use old Torzon links I saved?
Only if the address matches one of the five verified addresses on this page exactly — every character. Torzon has maintained the same five verified addresses since its August 2023 infrastructure update. Links saved before that date may not match. But links saved from third-party sources — Telegram groups, clearnet aggregators, Reddit posts — should be treated with skepticism regardless of age. Compare your saved address character by character against what's listed here. A match: fine to use. Any difference: don't. Verify through Dread's PGP-signed announcement first. That's the only authoritative source.
03
How quickly are new links published here?
This directory is reconciled twice daily against Torzon's PGP-signed announcements on Dread. When Torzon rotates an address — typically because one has been repeatedly targeted — the change appears in a new signed post within hours. We add the replacement within 12 hours of the signed announcement, after verifying the GPG signature against Torzon's known public key. We don't add addresses from any other source, and nothing goes live without a verified signature. Speed matters less than accuracy here. A wrong address is worse than a 12-hour delay. The process is deliberate.
04
Should I use the primary link or a mirror?
Either. All five addresses connect to the same backend — same listings, same wallet state, same account data, same order history. "Primary" just means it's listed first in Torzon's signed announcements. There's no technical distinction. Address 01 handles slightly more incoming traffic and may occasionally be marginally slower during peak hours — the difference is tenths of a second. Start there. If it's slow or unresponsive, switch to any other. Bookmark all five so you always have a fallback without needing to return to this directory. The access tutorial covers how to store verified addresses in KeePassXC so the autofill works for any of them.
05
Can I trust onion links from Telegram groups?
No. Telegram groups sharing Torzon links are a primary phishing vector. Groups claiming to offer "official Torzon links" or "emergency mirrors" are routinely operated by phishing actors, or infiltrated by them shortly after creation. Addresses posted there are frequently single-character substitutions of the real addresses — they resolve to convincing clones designed to harvest login credentials and drain wallets. The EFF's security research on darknet phishing operations consistently identifies Telegram as the leading distribution channel for fake links. Always source links from PGP-verified directories. If you can't verify the PGP signature yourself, use a directory that publishes its verification process. And treat any unverified link as a potential phishing address until proven otherwise.
Ready to access
Get the verified Torzon address
All five verified mirrors are listed above. Copy the primary address, open Tor Browser, paste. Haven't set up Tor yet — the access tutorial walks through every step.