IMMEDIATE ANSWER
What is a VPN kill switch?
A kill switch is a client control designed to restrict ordinary internet traffic if the VPN tunnel drops. Its purpose is to reduce accidental fallback to the normal network route.
Availability varies by app and platform. Current VPN-Accounts guidance verifies Network Lock on Windows for OpenVPN and a Network Lock setting on Android; it does not claim equivalent support everywhere.
How a VPN kill switch works
Without a traffic-blocking control, an operating system can return to its ordinary route after a VPN tunnel disconnects. Apps may continue reconnecting, and destinations can then receive the normal public IP. A kill switch or Network Lock applies client or operating-system rules intended to prevent that fallback traffic.
Implementation matters. Some controls block all connectivity until the tunnel returns; others apply only while connecting, to selected apps or to a particular protocol. The name alone does not establish identical behavior across clients.
Why it can matter
Network changes
Moving between Wi-Fi and mobile data, waking a device or passing through a captive portal can interrupt a tunnel. A correctly operating kill switch may deliberately pause traffic during that gap.
Unstable shared networks
Hotels, airports and cafés can drop or renew connections. Network Lock can reduce unnoticed fallback, while the broader public Wi-Fi checklist still applies.
Long-running applications
Browsers, sync tools and messaging apps may reconnect automatically. A kill switch is useful when the user's requirement is “do not send ordinary traffic unless the tunnel is active.”
Current verified VPNClient availability
Windows
The current Windows VPNClient includes Network Lock (Internet kill switch) for OpenVPN connections. Current project guidance does not present it as enabled by default or as a guarantee against every leak.
Android
The current Android VPNClient General settings include Network Lock and a separate reconnect option. The verified screen does not establish a universal default state or protocol-specific behavior.
macOS, iOS, Linux and manual configurations
Equivalent kill-switch behavior was not verified for these current VPN-Accounts setup paths. This guide therefore does not advertise it on those platforms. Built-in operating-system “always-on” or blocking controls may exist, but they are not treated here as the same VPNClient feature.
What happens when Network Lock activates
The internet may appear to stop. That can be the intended result: ordinary traffic is being restricted because the tunnel is unavailable. Reconnect the VPN, confirm the selected protocol is supported, and try another current server if appropriate.
Sleep, wake, captive portals and network switching are important test cases. Behavior can differ by operating system and version, so test the specific client before relying on it for sensitive work.
Limitations
- It does not create anonymity or hide logged-in account identity.
- It does not prevent phishing, malware, unsafe downloads or account compromise.
- It may interrupt connectivity by design.
- It may not cover every protocol, app, device state or manual setup identically.
- It does not replace HTTPS, software updates or multi-factor authentication.
- It cannot protect traffic sent before the VPN connects or after the feature is disabled.
Test rather than assume
- Install through the current setup guide.
- Enable the verified Network Lock setting on a supported client.
- Connect the VPN and confirm the expected public IP.
- Deliberately disconnect the tunnel during a non-sensitive test.
- Confirm ordinary traffic is restricted as expected.
- Reconnect, then test sleep/wake and network switching if those scenarios matter.
- If connectivity does not return, follow VPN Not Working rather than weakening unrelated device security.
Kill switch, reconnect and DNS are different controls
Auto-reconnect attempts to restore a tunnel. Network Lock restricts fallback traffic. DNS settings determine how name lookups are handled. A client may expose more than one of these controls, and enabling one does not prove the others work in a particular way.
For the wider privacy model, see VPN privacy and security. For restrictive-network connection behavior, read Stealth and VPN obfuscation.
Current account details
VPN-Accounts.com supports up to 10 simultaneous connections. The monthly plan starts at $7 with no long contract, includes setup support and carries a qualified 30-day money-back guarantee under the applicable terms. Kill-switch availability remains client- and platform-specific.
Useful answers
Frequently asked questions
What is a VPN kill switch?
A kill switch is a client feature designed to restrict ordinary network traffic if the VPN tunnel drops, reducing accidental fallback to the normal connection.
Does VPN-Accounts.com currently support a kill switch?
Current project guidance verifies Network Lock in the Windows VPNClient for OpenVPN connections and a Network Lock setting in the Android VPNClient. Equivalent behavior is not claimed for macOS, iOS, Linux or manual configurations.
Why can the internet stop when Network Lock is enabled?
Blocking connectivity while the tunnel is unavailable is the intended behavior. Reconnect the VPN or use the current troubleshooting guide; do not assume the feature is broken merely because ordinary traffic is blocked.
Does a kill switch make a user anonymous?
No. It can reduce accidental fallback traffic, but accounts, cookies, fingerprints, GPS, payments and information submitted to services can still identify a user.
Can a kill switch stop phishing or malware?
No. It does not verify destinations, remove malicious software or protect credentials entered into a fake page. HTTPS and device security remain separate.