> Torzon Mobile Mirror Endpoints
Three independent Torzon onion mirrors hosted in distinct relay regions. Each endpoint is reachability-probed every 15 minutes from handsets on filtered carriers, not just from servers. The full address list is signed with our PGP key. Last mobile reachability sweep: UTC
MOBILE REACHABILITY MONITOR - PER REGION, PER TRANSPORT
Probes connect from handsets inside three of the most aggressively filtered mobile networks we have access to. Latency is measured circuit-end-to-end over cellular through the indicated transport.
PGP-SIGNED ADDRESS LIST
The only mathematically reliable way to confirm an onion address came from us. On a phone, verify the signature with OpenKeychain on Android or the documented iOS workflow. Reject any list whose signature does not validate against the fingerprint below.
MOBILE ADDRESS HYGIENE CHECKLIST
Three checks every reader should run on the phone before pasting any onion address into Orbot's Tor Browser or Onion Browser.
Source Discipline
Bookmark this page in your mobile browser and revisit it before each session. App stores, chat groups and paste sites are seeded with phishing replicas, especially after a visible mobile block.
Signature Validation
Apply our PGP public key against the signed address bundle using OpenKeychain on Android. A valid signature is the only authentic chain of trust.
v3 Onion Format
Every authentic Torzon endpoint is exactly 56 base32 characters before .onion. v2 addresses (16 characters) are deprecated and should be treated as hostile.
Users frantically searching for a "fresh torzon link" on a phone after a carrier block rolls out are the highest-value targets. Operators of phishing replicas know exactly when mobile censorship intensifies and seed bridge channels with replacement addresses that capture credentials silently.
- NEVER trust onion addresses dropped in mobile chat groups or bridge channels
- NEVER open one unless the full 56-character address matches one of the three above byte-for-byte
- ALWAYS validate the PGP signature on the address bundle, not just the display on this page
- ALWAYS bookmark this page on your phone and return to it whenever you need a fresh endpoint
WHY THREE MIRRORS MATTER MORE ON MOBILE
Single-endpoint onion services fail the moment one upstream provider buckles under throttling or coordinated AS-level filtering - and on a phone you cannot easily switch to a second device.
Mirrors α, β and γ run in three distinct hosting regions, on three independent network paths, with three separate guard relay sets. We design around the assumption that any one region will eventually become unreachable - temporarily blocked, throttled, or slow. When that happens the remaining mirrors keep responding, and the mobile reachability monitor above reflects which one to use right now from a handset.
The pairing between mirror and transport is not arbitrary. Mirror α sits behind upstream relays that handle obfs4 traffic with the lowest jitter, so phone users on carriers that DPI-fingerprint Tor TLS get the best experience here. Mirror β is tuned for snowflake's WebRTC churn, suiting users whose carriers burn bridge IPs constantly. Mirror γ is the only endpoint we recommend behind meek-azure - useful when filtered Wi-Fi whitelists HTTPS to large CDNs and nothing else.
All three are Tor v3 onion services (56-character addresses) with end-to-end encryption from your phone's browser to the onion service backend. None of them ever exit Tor, so no clearnet observer - including a cooperating CDN or your mobile carrier - sees the request payload. Our job is simply to keep the entrance reachable from a handset. Once the mirror responds, what lies behind is identical regardless of which endpoint you used.
FIRST TIME CONNECTING FROM A PHONE?
The mobile setup guide covers Orbot on Android, Onion Browser on iOS, QR bridge import and the procedure for switching transports when a carrier starts throttling.
Open the Mobile Setup Guide