TorZon Market Link — Current Onion Addresses & PGP Verification

Every working TorZon market link is a 56-character v3 .onion address signed with the administration's OpenPGP key. Search results and forum comments are full of vanity clones that copy the first few letters of the real hostname to steal logins and swap deposit addresses. Below are the primary TorZon onion address and backup mirrors from the latest signed announcement, followed by the exact GnuPG and Kleopatra steps to verify them yourself.

Updated 2026-10-31 — Addresses checked against the market's PGP-signed mirror notice as of October 31, 2026.

Primary: torzonqh7epo5him7okkkkhfzdxlwh7f55wr4nhprjdoiskzdyjercid.onion
Mirror #1: torzonnjqpeln6fdiae3o57kcyzn6sq4yye7wf2bjfn6bs3nsipvmlid.onion
Mirror #2: torzonpippjluhbgekljuw2m5fvva5a3s6qwimcjhk66ppwikkzw5uid.onion

Market PGP Key & Fingerprint

TorZon's administrators sign every official mirror rotation and status notice with their master OpenPGP key. Before you trust any signed message, import the public key block below into GnuPG or Kleopatra and check its full 40-character hex fingerprint against at least two separate public records (such as the Dread subdread header and a previously saved copy from inside the market).

Expected fingerprint: 567B CEC7 2270 BE13 E413 8748 B457 F3DC D063 3200 — Ed25519 / Curve25519, generated September 2022.

Why the full 40-character fingerprint matters: Never rely on the display name attached to a PGP key or only the last 8 characters (the short key ID). Anyone can create a brand-new key named "TorZon Admin" in five seconds, and GPU tools can brute-force a matching 8-character short ID. Comparing all 40 hexadecimal characters is what guarantees you are checking against the real signing key.

How to Verify an Address

Checking a signed mirror list takes less than a minute once the market's public key is in your local keyring. Do this check locally on your own machine — never paste a signed block into a web-based "online PGP verifier," which can return a fake green checkmark while logging your activity.

1. Import the Key & Confirm the Fingerprint

Save the ASCII-armored public key block to a text file such as torzon-key.asc. In a terminal with GnuPG installed, run gpg --import torzon-key.asc and then gpg --fingerprint to print the full 40-character fingerprint. If you use Kleopatra on Windows or Linux, open File → Import Certificates, select the file, double-click the imported certificate, and read the 40-character fingerprint line by line.

2. Verify the Cleartext-Signed Mirror Announcement

Copy the entire signed mirror announcement — starting from -----BEGIN PGP SIGNED MESSAGE----- all the way down through -----END PGP SIGNATURE----- — and save it as mirrors.txt without adding or stripping blank lines. In GnuPG, run gpg --verify mirrors.txt. In Kleopatra, copy the signed block to your clipboard and choose Clipboard → Decrypt/Verify.

3. Check the Cryptographic Output (Watch Out for Spoofed Text)

A valid check prints gpg: Good signature from... followed by Primary key fingerprint: matching the exact 40-character string you verified in Step 1. Note that GnuPG will often print WARNING: This key is not certified with a trusted signature! — that warning only means you have not personally marked the key as "ultimately trusted" in your local web-of-trust settings; what matters is that the Good signature line and the 40-character fingerprint match. Be careful of a classic phishing trick where scammers type fake Good signature status lines directly into the body of a message signed by a throwaway key — the deeper walkthrough of GnuPG output, key generation, and spoofed-output traps sits in our OpenPGP signature verification guide.

4. Compare Both Ends of the 56-Character String in Tor Browser

Once the signature checks out, copy the 56-character .onion hostname directly from inside the verified message into Tor Browser. Because vanity generators can only match the first 6 to 8 characters of an onion address (torzon...) and never the entire 56-character Ed25519 string, glance at both the first 8 and the final 10 characters before .onion in the address bar before entering your username. For full operating-system and browser hardening steps, see our Tor Browser & PGP safety guide.

Where Signed Mirror Lists Are Published

TorZon's operators do not run clearnet domains, Telegram channels, or email newsletters. Authentic mirror updates originate from two signed sources: the official TorZon subdread on the Dread forum (where administrators post PGP-signed mirror tables and outage notes) and the signed mirror page / pgp.txt file hosted inside the market itself, which existing users can bookmark during an active session.

Phishing operators target users when the primary address slows down during a DDoS wave. If a mirror times out, never search a clearnet engine for a "new TorZon link" and never click an "emergency backup mirror" sent in a forum reply or private message. Instead, request a New Tor Circuit in Tor Browser or switch to one of the secondary mirrors from a signed announcement you have already verified — and when the failure is upstream, with an ISP or firewall blackholing Tor's public guards, the obfs4 and Snowflake bridges guide covers the workaround. Common connection errors and phishing red flags are covered in the TorZon Market FAQ.

Why TorZon Rotates Secondary Mirrors

How primary v3 addresses and rotating backup descriptors split traffic during DDoS attacks

Diagram comparing primary onion address, secondary mirrors, and rotating descriptors

The Primary Address vs. DDoS Congestion

In the Tor v3 protocol, a hidden service publishes encrypted descriptors to distributed directory nodes pointing to specific introduction points. When attackers launch a denial-of-service campaign against a market, they flood the introduction points of its best-known address with junk rendezvous requests so legitimate Tor Browser circuits time out before the login screen can load. The descriptor format and the full rendezvous path are dissected in our Tor v3 onion address anatomy.

TorZon's primary address (torzonqh7...ercid.onion) stays fixed over long periods so users have a stable reference point, which also makes it the main target whenever DDoS bots ramp up traffic.

How Secondary & Rotating Mirrors Work

Secondary mirrors are separate 56-character v3 Ed25519 keys that establish their own independent introduction points on the Tor network while routing into the exact same backend server, account database, and escrow wallets. Logging in through a verified secondary mirror opens the same account as the primary link.

When a secondary mirror gets bogged down by sustained bot traffic, the administrators retire that descriptor and publish a fresh PGP-signed mirror list. For context on how this setup helped the market survive the 2024–2025 outages that took down older platforms, see TorZon Market's history.