The mobile access reference for the Torzon onion service. Most people in restrictive networks own a handset before a desktop, so this site documents the phone path first: Orbot on Android and Onion Browser on iOS, bridges imported by QR code, and the obfs4, snowflake and meek-azure transports that defeat mobile deep-packet inspection on cellular carriers and filtered Wi-Fi.
Per-app routing and QR bridge import re-verified against all three mirrors on Android.
Fresh obfs4 set encoded as a scannable QR for offline transfer to a censored handset.
Built-in obfs4 and snowflake bridge entry confirmed working on current iPhones.
Three independent .onion endpoints, each reachability-tested every 15 minutes from handsets on filtered carriers. On a phone, always paste into the browser address bar by copy-and-paste and verify the address against our PGP fingerprint before trusting it.
Pick the mirror with the lowest latency from your mobile transport.
Lowest jitter behind obfs4 - the best default for Orbot on most mobile carriers.
Snowflake-friendly endpoint - recommended when a carrier burns bridge IPs quickly.
meek-azure path - useful on locked-down Wi-Fi that only permits HTTPS to big CDNs.
Only use addresses published on this signed page. App stores, chat groups and "fresh link" posts are routinely seeded with phishing replicas aimed at phone users who panic-search for a working entry point after a mobile block.
Everything here is the mobile connectivity layer - how to reach a Tor v3 onion service from a handset when the network in front of you is hostile. No transactions, no listings, no payment processing. Four pillars below.
VPN-mode or per-app routing, with bridge lines pasted or scanned from QR.
Built-in obfs4 and snowflake bridges with a Standard / Safer / Safest slider.
PGP-signed obfs4 bundles encoded as QR so nothing is typed on a small keyboard.
OpenKeychain on Android and an iOS workflow to check the signed mirror manifest.
Reports from people who reach Torzon from a handset behind hostile carriers and filtered Wi-Fi. Not endorsements - descriptions of which mobile transport defeated which block. Browse the mobile features referenced here.
No laptop in this region, handset only. Orbot kept stalling on plain bridges, so I scanned the QR obfs4 bundle from this page on a friend's phone. First connect on the second attempt. Mirror α has been steady on mobile data since.
Campus Wi-Fi blocked everything except HTTPS to big providers. Onion Browser's built-in snowflake got me out; meek behaved worse on iOS as the page warned. Mirror β reachable, slower but usable for reading.
Worried about battery and data on a prepaid plan. The published battery profile matched what I saw - idle snowflake drain is real, so I switched to per-app Orbot and only ran Tor Browser for Android. Much easier on the meter.
Wanted to verify the mirror manifest without a computer. OpenKeychain imported the public key and checked the detached signature right on the phone. Fingerprint matched the one printed on every page. Good signature, trust established.
If every mobile transport fails on your carrier, send your country, your handset OS and the symptoms you see. We can often suggest a private bridge or a fresh QR bundle. PGP-encrypted messages preferred.
Torzon Onion is the mobile access reference in front of the Torzon onion service. The service itself runs on three Tor v3 hidden services in geographically separate regions. This site publishes the authenticated mirror addresses, distributes a signed obfs4 bridge bundle as a phone-scannable QR, and documents how Orbot and Onion Browser reach those mirrors. We do not operate the marketplace's escrow or vendor systems - we only document how to reach the onion service from a handset.
Anyone on a free, neutral connection can reach Torzon through Tor Browser without any of this. This reference exists for the phone-only case: residents of regions where carriers block guard IPs, students on locked-down campus Wi-Fi, travellers on hotel networks that only allow HTTPS to known CDNs, and people whose only device is the phone in their pocket. For them, a desktop walkthrough is useless.
For those readers we keep current obfs4 bridge bundles in QR form, tested obfs4 / snowflake / meek-azure settings for both mobile apps, a documented battery and data profile, and a mobile PGP verification workflow. Begin with the mobile setup guide; it walks Orbot and Onion Browser from a blocked phone down to a working circuit.
In most censored regions the phone is the only computer people own. A desktop-only guide leaves them stranded; this reference treats the handset as the primary device.
Orbot configurations with obfs4, snowflake and meek-azure, plus QR import so a bridge line never has to be typed on a touchscreen keyboard.
Onion Browser documented honestly: obfs4 and snowflake work well, meek-azure is constrained by Apple networking limits. No false promises about iOS.
Measured cellular data and battery cost per transport, so a user on a prepaid plan can pick a setting that does not drain the meter or the battery.
A condensed walk-through. The full mobile setup guide covers each step with per-app screenshots and settings.
Android: install Orbot from F-Droid or Google Play. iOS: install Onion Browser from the App Store. Install only from the official stores - repackaged builds ship hostile bridge defaults.
Open the bridge settings, paste an obfs4 line or scan our signed QR bundle. On Android, Orbot scans the QR directly; on iOS, Onion Browser accepts a built-in obfs4 or snowflake bridge.
obfs4 for ordinary carrier DPI, snowflake when bridge IPs are burned quickly, meek-azure on Wi-Fi that only allows HTTPS to known CDNs. Switch on first sign of throttling.
Paste the mirror with the lowest latency from your transport. Mirror α suits obfs4, β suits snowflake, γ suits meek-azure. Verify the address against the PGP fingerprint first.
Install Orbot from F-Droid or Google Play, open Settings then Bridges, and paste an obfs4 line or scan our QR bundle. Turn on VPN mode for the whole phone, or per-app mode for Tor Browser for Android only, then open a mirror address.
Yes. Install Onion Browser from the App Store. It ships built-in obfs4 and snowflake bridges; meek-azure is limited on iOS by Apple's networking rules. Configure a bridge on first launch, connect, then load a mirror.
snowflake holds a WebRTC connection open and draws more battery and data than obfs4. On a prepaid plan, prefer obfs4 in per-app mode so only Tor Browser for Android is routed. Our features page has the measured profile.
Use OpenKeychain on Android (or the documented iOS workflow) to import our public key and check the detached signature on the mirror manifest. The fingerprint must read 4B9E 1C7A F25D 8063 A4E7 9F31 6C28 B5D4 0E71 38FA.
Every mobile block we have documented in 2026 - carrier DPI, burned bridge IPs, CDN-only Wi-Fi - has a working countermeasure on this site. Start with the mirror endpoints and the phone setup guide.
View Mirror Endpoints