SwizGuard

A self-hosted "Stealth VPN" implementation, forked from xray-core and WireGuard. It makes your traffic look like normal TLS traffic but little does your ISP know there is an entire encrypted WireGuard tunnel in there...

Not yet testedsource: GitHubShellMITcommit 39ff1af1f9e0

Shell, MIT licensed. The project labels itself: censorship circumvention, censorship resistance, obfuscation, privacy, selfhost, sing box, stealth and tls.

SwizGuard has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
224
forks
27
open issues
4
watchers
2
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

censorship-circumventioncensorship-resistanceobfuscationprivacyselfhostsing-boxstealthtlsvlessvpnvpswireguard

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/SwizGuard.svg)](https://argusic.com/subject/swizguard)

Questions

Does SwizGuard run?
SwizGuard has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test SwizGuard?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for SwizGuard?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion