[{"data":1,"prerenderedAt":41},["ShallowReactive",2],{"blog-post-the-tools-that-keep-the-open-web-open":3},{"id":4,"meta":5,"title":21,"author":22,"body":26,"introduction":33,"date":34,"tags":35,"category":39,"blog_image":40,"intro":33,"featured":10},1294,{"type":6,"detail_url":7,"html_url":8,"slug":9,"show_in_menus":10,"seo_title":11,"search_description":11,"first_published_at":12,"alias_of":13,"parent":14},"blog.BlogPage","https:\u002F\u002Fwww.staging.doprax.rocks\u002Fd\u002Fapi\u002Fv2\u002Fpages\u002F1294\u002F","https:\u002F\u002Fwww.staging.doprax.rocks\u002Fd\u002Fdoprax-blogs\u002Fthe-tools-that-keep-the-open-web-open\u002F","the-tools-that-keep-the-open-web-open",false,"","2026-07-10T15:16:02.582295Z",null,{"id":15,"meta":16,"title":20},109,{"type":17,"detail_url":18,"html_url":19},"blog.BlogIndexPage","https:\u002F\u002Fwww.staging.doprax.rocks\u002Fd\u002Fapi\u002Fv2\u002Fpages\u002F109\u002F","https:\u002F\u002Fwww.staging.doprax.rocks\u002Fd\u002Fdoprax-blogs\u002F","Doprax Blogs","The Tools That Keep the Open Web Open",{"id":23,"username":24,"full_name":25},5,"Swetlana","Swetlana A",[27],{"type":28,"value":29,"id":32},"section",{"title":11,"content":30,"subsections":31},"\u003Cp data-block-key=\"flj9e\">Blocking the internet is harder than it sounds. Cut off one protocol, and people switch to another. Block that one, and developers build a new one. Block entire IP ranges, and someone routes traffic through a CDN the censor can't touch without also taking down half the domestic economy. This cycle has been running for years, and the tools it has produced are more sophisticated, more creative, and more resilient than anything that existed a decade ago.\u003C\u002Fp>\u003Cp data-block-key=\"87rd0\">This post is a map of that landscape. It covers the main tools people use to reach the open web from restricted networks, how they work under the hood, and why some survive blocking attempts that others don't. Each tool in the list links to a setup guide so you can run your own node and contribute capacity to the network.\u003C\u002Fp>\u003Ch2 data-block-key=\"b63mg\">Why commercial VPNs keep failing\u003C\u002Fh2>\u003Cp data-block-key=\"c6k72\">Standard VPN protocols (WireGuard, OpenVPN, IKEv2) have recognizable packet signatures. A network running deep packet inspection (DPI) can identify them within seconds and drop the connection. This isn't theoretical — WireGuard went from reliable to blocked across multiple major censored networks within months of widespread adoption, because its traffic is statistically distinctive even when encrypted.\u003C\u002Fp>\u003Cp data-block-key=\"5ppo8\">The response has been a generation of tools that don't try to hide that they're doing something, but instead make what they're doing look like something else entirely, usually HTTPS traffic to a legitimate web service.\u003C\u002Fp>\u003Ch2 data-block-key=\"4njqd\">The current toolkit\u003C\u002Fh2>\u003Ch3 data-block-key=\"1ndo2\">Psiphon\u003C\u002Fh3>\u003Cp data-block-key=\"1dhc9\">Psiphon combines VPN, SSH, and HTTP proxy technologies and dynamically selects whichever works on a given network. Its defining feature is a managed network of proxy servers that rotate automatically when blocked. Users don't configure anything; the app handles failover transparently.\u003C\u002Fp>\u003Cp data-block-key=\"dq3os\">During a major internet shutdown in early 2026, Psiphon stayed functional when most other tools had been neutralized. Part of the reason is Psiphon Conduit: a companion app that lets anyone outside the restricted network share a portion of their bandwidth as a relay. More conduit nodes means more entry points, and each entry point has a different IP address that censors would need to identify and block individually.\u003C\u002Fp>\u003Cp data-block-key=\"84in5\">\u003Ca href=\"\u002Fd\u002Fdoprax-docs\u002Frun-a-psiphon-conduit-node-on-a-doprax-provm\u002F\">How to run a Psiphon Conduit node on a ProVM\u003C\u002Fa>\u003C\u002Fp>\u003Ch3 data-block-key=\"78edi\">Tor and obfs4 bridges\u003C\u002Fh3>\u003Cp data-block-key=\"9r87o\">Tor routes traffic through a network of volunteer-operated relays. The public relay list is well-known and heavily blocked on networks that care. Bridges solve this: they're unlisted Tor entry points, distributed through out-of-band channels (email, a website, personal sharing) rather than published openly.\u003C\u002Fp>\u003Cp data-block-key=\"85rqi\">obfs4 goes further. It's a pluggable transport that disguises Tor traffic so it doesn't look like Tor traffic at all. A network doing DPI on a connection using an obfs4 bridge sees something that resembles random noise, not a recognizable protocol signature.\u003C\u002Fp>\u003Cp data-block-key=\"eikfh\">The Tor Project expects its Snowflake transport to continue working even under whitelist-based blocking (where only pre-approved IPs and domains are allowed through), because Snowflake uses WebRTC, which is difficult to block without also breaking real-time communication across most of the web.\u003C\u002Fp>\u003Cp data-block-key=\"3feib\">\u003Ca href=\"https:\u002F\u002Fwww.doprax.com\u002Ftutorial\u002Fhow-to-run-a-tor-bridge-on-a-doprax-provm\">How to run a Tor obfs4 bridge on a ProVM\u003C\u002Fa>\u003C\u002Fp>\u003Cp data-block-key=\"f4ea\">\u003Ca href=\"\u002Fd\u002Fdoprax-docs\u002Frun-a-tor-snowflake-proxy-on-a-doprax-provm\u002F\">How to run a Tor Snowflake proxy on a ProVM\u003C\u002Fa>\u003C\u002Fp>\u003Ch3 data-block-key=\"dcfs2\">Lantern\u003C\u002Fh3>\u003Cp data-block-key=\"c9hr9\">Lantern looks like a VPN from the user's perspective, but its core technique is different. It uses TLS record fragmentation: the initial TLS handshake is split into multiple records so that the Server Name Indication (SNI) field, the part that tells a filter what domain you're connecting to, is fragmented across those records. Many automated filtering systems can't reassemble and inspect the SNI in fragmented records, so the connection goes through without a proxy.\u003C\u002Fp>\u003Cp data-block-key=\"db0b1\">When fragmentation isn't enough, Lantern falls back to a volunteer proxy network called Lantern Unbounded, where users outside restricted networks share bandwidth in the same model as Psiphon Conduit.\u003C\u002Fp>\u003Ch3 data-block-key=\"423u8\">Snowflake\u003C\u002Fh3>\u003Cp data-block-key=\"7bt38\">Snowflake is a Tor pluggable transport, but worth calling out separately because its architecture is different from traditional bridge infrastructure. Instead of a fixed server that can be blocklisted, Snowflake uses temporary WebRTC proxies operated by volunteers in browser tabs or on servers. Each proxy exists briefly, handles a few connections, and disappears. There's no stable IP to block.\u003C\u002Fp>\u003Cp data-block-key=\"dsc7u\">Running a Snowflake proxy requires almost nothing, a browser extension is enough, but running one on a persistent server means it stays available continuously and serves more users.\u003C\u002Fp>\u003Cp data-block-key=\"e029l\">\u003Ca href=\"\u002Fd\u002Fdoprax-docs\u002Frun-a-tor-snowflake-proxy-on-a-doprax-provm\u002F\">How to run a Tor Snowflake proxy on a ProVM\u003C\u002Fa>\u003C\u002Fp>\u003Ch3 data-block-key=\"6v5a8\">Warp-plus (Cloudflare Warp + Psiphon chaining)\u003C\u002Fh3>\u003Cp data-block-key=\"1rad8\">This one is a product of the Iranian open-source community specifically. Warp-plus implements Cloudflare's WARP protocol and chains it with Psiphon for environments where WARP alone gets blocked. It also supports \"gool mode\" (warp-in-warp): two WARP instances chained together to change the user's virtual NAT location before applying the obfuscation layer.\u003C\u002Fp>\u003Cp data-block-key=\"c9p1k\">The project is maintained on GitHub (the primary fork is at github.com\u002Fbepass-org\u002Fwarp-plus) and has several active community forks. It runs cleanly on a standard Linux VM.\u003C\u002Fp>\u003Cp data-block-key=\"9vhv7\">How to run a Warp-plus server on a ProVM → \u003Ci>(coming soon)\u003C\u002Fi>\u003C\u002Fp>\u003Ch2 data-block-key=\"dnr4e\">What actually survives a whitelist\u003C\u002Fh2>\u003Cp data-block-key=\"9hcha\">Most circumvention tools work against DPI-based blocking, where traffic is inspected and dropped if it matches a pattern. A whitelist is different: only traffic to pre-approved IP addresses and domains gets through. Everything else is blocked by default.\u003C\u002Fp>\u003Cp data-block-key=\"bi2ej\">Under a whitelist, tools that route through CDN infrastructure (Cloudflare, Google, AWS) have a survival advantage because blocking those IPs would take down domestic services that depend on the same infrastructure. Tools that use WebRTC (Snowflake) are also harder to block because WebRTC is the backbone of video calls, which censors generally want to allow.\u003C\u002Fp>\u003Cp data-block-key=\"1ju19\">Plain VPNs, Tor over standard protocols, and most proxy tools don't survive a whitelist. obfs4 bridges with non-datacenter IPs have a better chance. Snowflake, WARP, and CDN-fronted transports have the best odds.\u003C\u002Fp>\u003Ch2 data-block-key=\"fot46\">How to contribute\u003C\u002Fh2>\u003Cp data-block-key=\"7gbi6\">Every node matters. A Tor bridge, a Psiphon Conduit instance, a Snowflake proxy running on an idle VM: each one adds capacity to a network that distributes access to the open web for people on restricted networks. The setup guides linked above walk through each option. All of them run on a ProVM with the smallest plan.\u003C\u002Fp>\u003Cp data-block-key=\"8d8tj\">\u003Ca href=\"https:\u002F\u002Fwww.doprax.com\u002Fvirtual-machines\u002F\">Start a ProVM in under a minute.\u003C\u002Fa>\u003C\u002Fp>",[],"d204f00e-6b1a-4022-9bf4-ca05c59a70ac","\u003Cp data-block-key=\"8u4cw\">sdfsd\u003C\u002Fp>","2026-07-10",[36,37,38],"cloudflare","psiphon","tor bridge","updates","\u002Fd\u002Fmedia\u002Foriginal_images\u002Fthe_tools_that_keep_the_open_web_open_doprax.png",1792480192277]