MyIPScan

Independent self-test

Windscribe Leak Test

Windscribe deliberately does not ship a kill switch. It ships a Firewall, and it argues the difference matters: a kill switch reacts after the tunnel drops, while the Firewall is on before that and blocks anything not going through the VPN. Its IPv6 handling is conditional rather than a flat yes or no, and it runs its own resolvers. The result speaks for your session only, not for Windscribe's network.

Read methodology

Live test

Run the test on Windscribe now

Windscribe ships a Firewall instead of a kill switch, and its IPv6 handling depends on protocol and location, so read the IPv6 line carefully.

Open the full VPN Leak Test

This browser session

Leak report

Not tested
Verdict
Visible IP
Not tested
DNS
Not tested
WebRTC
Not tested
IPv6
Not tested
Browser
Not tested
Next step

This reports what your browser shows in this session. It does not certify Windscribe, does not test every server, app or device, and does not prove anonymity.

Current-session checks

What this Windscribe self-test checks

Read the signals once unconnected and once connected. On Windscribe the lines worth studying are IPv6, which depends on your protocol and location, and DNS, which Windscribe answers itself.

Before you read the result

What Windscribe documents about these signals

Windscribe's feature pages and knowledge base state each point below, and its wording about kill switches is deliberate rather than accidental.

A Firewall instead of a kill switch

Windscribe states that it does not have a kill switch and uses a built-in Firewall instead, on the grounds that a kill switch is reactive and only acts after the VPN has gone down, while the Firewall works continuously to block traffic not going through the VPN. The setting lives under Preferences, Connection, Firewall Mode, and it is the first thing to check after an unexpected reading.

IPv6 depends on protocol and location

Windscribe documents IPv6 as conditional: it can route IPv6 through the tunnel on WireGuard, on paid locations where the app and the server support it, and otherwise it blocks IPv6 to prevent a leak. So both an IPv6 answer and an empty IPv6 line can be correct on Windscribe - which one you get depends on the protocol and the location you chose.

Windscribe answers DNS itself

Windscribe says it uses its own internal DNS servers, which become active when you connect, and that all DNS queries travel over the tunnel. R.O.B.E.R.T. is the blocking layer built on top of that, filtering ad, tracker and malware domains at resolution time - which can also explain a resource that will not load during a check.

WebRTC and the browser extension

Windscribe is explicit that WebRTC can read the local address and bypass a browser proxy, which is why its extension carries a WebRTC Slayer switch. It also notes this is a browser-proxy problem rather than a desktop-app one: with the whole system routed through the desktop app, WebRTC has no separate path out. Which of the two you are using changes how to read the WebRTC result.

An audit published without redactions

Windscribe commissioned Packetlabs to audit its FreshScribe stack in 2024, covering roughly twenty repositories and around eighty thousand lines of code including its own forks of OpenVPN and WireGuard, and published the report unredacted. Like every audit, it describes the provider's systems at a point in time rather than your session.

Between the readings

Record a kill-switch drop on Windscribe

Windscribe argues that the difference between its Firewall and a kill switch is timing: one is blocking before the tunnel drops, the other reacts after it. Timing is exactly what a recorded drop measures.

Known leak issues and fixes

How Windscribe stands against the VPN leak attacks published since 2023, and leak bugs the provider disclosed itself, taken from its own statements and changelogs. Every row links to its source and says when we last read it. Compare every provider side by side.

AttackAppsStatusWhat the provider saidSource
TunnelVisionCVE-2024-3661 All apps Not statedChecked 8 Apr 2026 Windscribe's firewall article does not mention TunnelVision, and no other statement was found. windscribe.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 All apps Not statedChecked 8 Apr 2026 No Windscribe statement found on its site or in its app releases. windscribe.comRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 8 Apr 2026 No Windscribe statement found on its site or in its app releases. windscribe.comRead 18 Oct 2026
Linux IPv6 DNS leak protection gap Linux FixedStated 6 Jul 2026Fix: 2.23.11 IPv6 DNS servers were missing from the leak protection rules. Changelog on GitHubRead 18 Oct 2026
DNS leak on Linux with resolvectl Linux FixedStated 30 Sep 2025Fix: 2.17.9 From Windscribe's desktop release notes. Changelog on GitHubRead 18 Oct 2026
IPv6 leak with WireGuard and Allow LAN Android FixedStated 9 Jul 2023Fix: 3.74 From Windscribe's Android release notes. Changelog on GitHubRead 18 Oct 2026

Latest app versions: Windows, macOS, Linux 2.24.13 (8 Sep 2026); Android 4.3 (1 Sep 2026); iOS 3.14.1 (25 Aug 2026).

These are the provider's published statements, not tests we ran. The leak test on this page checks your own connection; these attacks need a hostile local network and cannot be reproduced from a web page.

Incidents on record

Security incidents and legal cases involving Windscribe, from its own statements or a primary document. Incidents across providers.

DateWhat happenedProvider’s responseSource
11 Apr 2025 A court in Athens dismissed criminal charges against Windscribe's founder over activity by an unknown user of a Windscribe server. Windscribe said it keeps no user activity logs, so there was nothing to hand over. cybernewswire.comRead 19 Oct 2026
24 Jun 2021 Ukrainian authorities seized two Windscribe servers whose unencrypted disks held an OpenVPN server certificate and key. Windscribe replaced its OpenVPN certificate authority and moved servers to in-memory operation. windscribe.com blogRead 19 Oct 2026

Published audits

Audits and tests Windscribe has published or announced, newest first. “What was checked” is the scope the audit itself states; anything outside it was not examined. Compare audits across providers or see all published VPN audits we track.

DateAuditorTypeWhat was checkedFindingsSource
Jun 2024 Packetlabs Servers and infrastructure The FreshScribe VPN server stack. Not published windscribe.comRead 18 Oct 2026
Mar 2022 Leviathan Security Apps Source review of the Android and iOS apps; Windscribe says all issues were fixed. Not published Report windscribe.comRead 18 Oct 2026
Sep 2021 Leviathan Security Apps Code review of the desktop client. Not published Report windscribe.comRead 18 Oct 2026

Who runs Windscribe, and on what

Company
Windscribe Limited, Canada. An Ontario company with a Toronto address. windscribe.comRead 18 Oct 2026
Open-source apps
Windscribe says all its apps are open source. Code windscribe.comRead 19 Oct 2026
Transparency, live monthly report
Counts load in the browser; Windscribe states it complied with no requests because it had no relevant data. windscribe.comRead 18 Oct 2026

Who owns which VPN: every provider’s company and the groups that run several brands.

What this cannot prove

  • This checks visible browser/session signals only.
  • This does not certify the provider.
  • This does not test every server, app, device, or connection.
  • This does not prove anonymity.
  • This does not prove every security condition.
  • A clean result does not prove every leak is absent.

How to compare before and after on Windscribe

  1. Take a reading on your normal connection: address, resolver, IPv6 and WebRTC.
  2. Connect with Windscribe and note two things - your Firewall Mode setting, and whether you are on WireGuard.
  3. Rerun the same checks in the same browser, and note whether you are relying on the desktop app or the browser extension.
  4. An IPv6 result is only meaningful once you know whether your protocol and location support IPv6 in the first place.
Safe Copy limits

Safe Copy exports use safe summary categories and remove raw IP, exact city, full user-agent, raw fingerprint data, raw resolver IPs and WebRTC candidates. It is not a certificate, provider audit, or proof of anonymity.

FAQ

Windscribe leak test FAQ

Does Windscribe have a kill switch?

Windscribe says it does not, and uses an always-on Firewall instead. It argues a kill switch is reactive and only acts after the VPN drops, while the Firewall continuously blocks traffic that is not going through the VPN.

Where is the Firewall setting?

Windscribe documents it under Preferences, Connection, Firewall Mode in the desktop app. It is the setting to confirm first when a check reports an address you did not expect.

Does Windscribe support IPv6?

Conditionally. Windscribe documents routing IPv6 through the tunnel on WireGuard for paid locations where the app and server support it, and blocking IPv6 otherwise so it cannot leak. Both an answer and an empty line can be correct depending on your setup.

Which DNS servers answer while I am connected?

Windscribe states that it uses its own internal DNS servers, active when you connect, with all queries travelling over the tunnel. R.O.B.E.R.T. does domain blocking at that layer.

Do I need WebRTC Slayer if I use the desktop app?

Windscribe describes WebRTC Slayer as an extension feature for the case where you are using the browser proxy only. With the whole system routed through the desktop app, it says WebRTC has no separate path out.

Has Windscribe's infrastructure been audited?

Windscribe had Packetlabs audit its FreshScribe stack in 2024, across roughly twenty repositories and around eighty thousand lines of code, and published the report without redactions. That covers the provider's systems, not your browser.