About the Torzon Gateway
An independent connectivity layer in front of the Torzon onion service. Operating since 2022, the Gateway publishes bridge relays, pluggable transport configurations, and geographically distributed mirror addresses for users whose networks restrict direct Tor access.
What this Gateway does
We document how to reach the Torzon onion service when a network is hostile to direct Tor connections. We do not run the marketplace, hold escrow, vet vendors or process any transaction. The Gateway exists so that an ISP-level block, a national firewall or a corporate proxy does not become the reason an onion service is unreachable.
Operating principles
The decisions that shape every page, configuration and bridge address we publish.
Verifiable, not promotional
Every onion address is published with a PGP-signed manifest. Every transport configuration we recommend was reproduced on probes inside the same kind of network we say it defeats. Where a claim cannot be verified we omit it rather than fill the page.
No data exhaust
No accounts, no cookies, no analytics, no third-party scripts, no CDN. Fonts and icons are served from this domain. The only network conversation a visitor has is HTTPS to torzon-gateway.guide and whatever they choose to do after leaving.
Adversarial neutrality
We document techniques that defeat censorship. Whose censorship is not our concern. The same bridge configuration that protects a journalist from a hostile regime protects a corporate employee from an over-reaching network team — and we describe both situations honestly.
Connectivity milestones
Visible changes in the connectivity surface. Marketplace milestones, vendor numbers and revenue figures are not ours to publish.
First published mirror address and signed bridge list. obfs4 was the only transport documented at launch. PGP fingerprint for the address manifest was generated and remains in use.
Two additional transport tracks documented after observing IP-enumeration of obfs4 bridges in two East-Asian networks. Snowflake bridge pool and meek-azure front configuration walked end-to-end.
Migrated from a single onion endpoint to three geographically distributed mirrors. Reachability probe infrastructure deployed in censored test networks so the status indicators on the home page reflect actual conditions inside the firewall, not edge of it.
Orbot and Onion Browser walkthroughs published so handset-only users reach the same three mirrors with the same transport options as desktop. QR import for bridge lines verified on both platforms.
Walkthrough for running a private obfs4 bridge on a $5/month VPS in a friendly jurisdiction. Targeted at users whose social graph (family, colleagues) keeps hitting the same blocks and benefits from a dedicated entry point.
Gateway in numbers
Connectivity metrics, measured from our probe network inside censored regions. Not marketplace metrics.
Contact
Connectivity failure reports, fresh symptoms from a new block, or PGP-signed corrections. Plain enquiries also welcome. Encrypted messages preferred.