TorZon Onion Addresses and Verification

These three strings are the complete TorZon address set published by TRZN Watch. Match all 56 characters before .onion; a familiar “torzon…” prefix alone is not enough.

Onion services can rotate or pause between sessions, so status is best read as a check sequence rather than a permanent badge. Start from the address set above, confirm Tor Browser itself is working, then open the matched destination and apply any signed-statement check that is available.

Diagnose Tor Browser with the Tor Project connection check and the Tor Browser setup guide. The CAPTCHA capture below is an authentic TorZon screen from the TRZN Watch archive of a live onion session.

1. Confirm the string is a complete v3 onion address and compare all 56 characters before .onion with the record on this page. The Tor Project overview explains how onion-service names relate to public keys.
2. When a signed address statement exists, take the expected public-key fingerprint from an independent source you already trusted. A key published only on the page under test is circular.
3. Verify the exact signed bytes locally with software such as GnuPG. Keep the command output, fingerprint, signed text, timestamp and source together.
4. Open the matched address over Tor. A live TorZon page, such as the CAPTCHA capture archived on this site, confirms the destination answered; keep that result together with the full-string match and any signature check.

For the full signature workflow, use the PGP verification guide. For vanity prefixes and visual clones, use the onion phishing guide.

TRZN Watch keeps prior rows visible when the published set changes, so readers can see what was shown on earlier review dates.

Attackers can copy layout, CAPTCHA screens and even a short “torzon” prefix. They cannot rely on readers comparing the complete address, and they cannot forge a private key that matches a fingerprint established out of band. That is why this page publishes the full strings and points to signature checks.

Historical cases where a service stayed usable after control changed are covered in the market-history guide. Use those lessons with the method above, not as a substitute for it.