VPN kill switch

Updated 21 September 2026 · How we research

A kill switch blocks your traffic when the tunnel is not up. It exists because the dangerous moment is not when a VPN is connected — it is the few seconds after it silently drops, when your device cheerfully falls back to the ordinary connection.

Kill switch: fail closed, not exposed

A kill switch is designed to stop unprotected traffic when the VPN tunnel drops.

  1. Tunnel connected

    Traffic follows the protected VPN route.

    PROTECTED PATH ACTIVE

  2. Tunnel drops

    The app detects a failed or interrupted connection.

    CONNECTION EVENT

  3. Traffic blocked

    Internet access stays blocked until protection returns.

    FAIL-CLOSED STATE

Test it

Record OS, app version, protocol, traffic type, drop method, observed IP/DNS behaviour and recovery time.

A firewall-level kill switch denies all traffic outside the tunnel until the tunnel is restored.

How it is implemented

A real kill switch is a firewall rule, not an application setting. The client installs a rule that permits traffic only on the virtual interface, plus the single route needed to reach the VPN server. If the interface goes away, nothing matches the permit rule and traffic stops.

Kill switches are operating-system features that clients drive. Where the OS offers its own control, prefer it.

PlatformMechanismPractical caveat
WindowsWindows Filtering Platform rulesGenerally robust, including across sleep and wake
macOSPacket filter or Network Extension rulesBehaviour on wake can vary between client implementations
Linuxiptables or nftables rulesStrongest when the client also handles reboot persistence
AndroidSystem "Always-on VPN" with "Block connections without VPN"The OS-level toggle is more reliable than an in-app switch
iOSNetwork Extension, with per-app VPN reserved for managed devicesThe OS may allow brief system traffic outside the tunnel

Use the Android system toggle

On Android, open Settings → Network & internet → VPN, select the app's gear icon, and enable both "Always-on VPN" and "Block connections without VPN". This is enforced by the operating system and survives the app being killed.

The failure modes worth testing

  1. Process crash. End the VPN client process from the task manager. Traffic should stop immediately, not continue.
  2. Network change. Switch from Wi-Fi to cellular, or disconnect and reconnect Wi-Fi.
  3. Sleep and wake. Suspend the machine for a few minutes and check what happens in the first seconds after it wakes.
  4. Reboot. Restart with the client set to autostart and see whether anything escapes before the tunnel comes up.
  5. Server change. Switch servers inside the app and watch for a gap during the handover.

Step-by-step verification is covered in how to test a VPN.

What ZoogVPN states

According to ZoogVPN

ZoogVPN describes its kill switch as preventing a device from accessing the unprotected internet, and says that if the connection unexpectedly fails it "will block internet access for an affected device until the connection to the VPN node is restored". It lists the feature on Android, iOS, Windows and macOS, enabled by a toggle in the app settings. The page does not state whether it is on by default, and we have not tested its behaviour.
ZoogVPN logoSave 82%

ZoogVPN lists kill-switch support across its Windows, macOS, Android and iOS apps.

$2.49/month+ 3 months free

2-year plans

Unlimited devices30-day guarantee

Affiliate link — we may earn a commission at no extra cost to you. See our affiliate disclosure. Pricing shown as published on VPN Sherlock; confirm current terms at checkout.

Frequently asked questions

Should I leave the kill switch on all the time?
On untrusted networks, yes. The cost is that your connection stops working when the VPN is down, which is the intended behaviour.
Why does my internet stop working after I quit the VPN app?
A firewall-level kill switch can leave its rules in place if the client exits uncleanly. Reopening the client and disconnecting properly normally clears them.