MyIPScan

Independent self-test

Mullvad Leak Test

Mullvad is unusual on three of the axes these checks measure. Its kill switch is always on and cannot be disabled in settings. IPv6 is a setting you turn on rather than one that is on already, on Windows and Linux. And Mullvad announces its exit addresses from its own autonomous system, so an ASN lookup names Mullvad rather than a hosting company. Everything below describes one browser on one connection; it settles nothing about Mullvad's fleet as a whole.

Read methodology

Live test

Run the test on Mullvad now

Mullvad cannot have its kill switch turned off and IPv6 is opt-in, so an empty IPv6 line is expected here. The network line should name Mullvad rather than your ISP.

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 Mullvad, does not test every server, app or device, and does not prove anonymity.

Current-session checks

What this Mullvad self-test checks

Work through the tools once before you connect and once after. On Mullvad the interesting comparison is the ASN behind your exit address and whether IPv6 answers at all, because both follow from choices Mullvad has made and documented.

Before you read the result

What Mullvad documents about these signals

These points come from Mullvad's help pages and its published audit posts, and they set the baseline your own result should be compared against.

A kill switch you cannot turn off

Mullvad's help pages describe the kill switch as always on and impossible to disable in settings: it is active from the moment you press Connect until you disconnect. Separately, an optional Lockdown mode keeps blocking the internet even after you press Disconnect or Quit. So on Mullvad there is no kill-switch toggle to blame for an unexpected reading - look at Lockdown mode and at what was running outside the app instead.

IPv6 is opt-in, not automatic

Mullvad states that on Windows and Linux IPv6 is normally not needed and is something you enable if you have a reason to, while on a Mac it should normally be enabled or some sites will not load. That means an empty IPv6 result on Windows usually reflects the default rather than a fault, and an IPv6 address appearing after you enabled the setting is expected.

The exit sits in Mullvad's own network

Mullvad announces address space from its own autonomous system, AS39351, rather than only reselling hosting capacity. That makes the ASN behind your exit address a usable confirmation: see AS39351 on MyIPScan for what a lookup returns, and the ranges Mullvad announces for the prefixes involved. Mullvad also documents using colocated hardware, so not every server is guaranteed to land in that ASN.

Custom DNS overrides the content blockers

Mullvad supports setting your own DNS server in the app's advanced settings, and documents that doing so overrides its DNS content blockers. It also notes that a public DNS server can only be used on WireGuard, while a local one works with OpenVPN. If a DNS check names something other than Mullvad, that setting is the first place to look.

Browser signals and published audits

WebRTC and fingerprint readings come from the browser, which the VPN app does not rewrite. Mullvad ships Mullvad Browser, built with the Tor Project as a Tor Browser without the Tor network, precisely because those signals live outside the tunnel. Mullvad also publishes audit reports: X41 D-Sec audited the app over 30 person-days in late 2024 and Cure53 completed a fourth infrastructure audit in June 2024.

Between the readings

Record a kill-switch drop on Mullvad

Mullvad's help pages describe a kill switch that is always on and cannot be disabled in settings. That makes a recorded drop a check of the outcome rather than of the checkbox: nothing to switch off, so watch what actually got out.

Known leak issues and fixes

How Mullvad 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 Windows, macOS, Linux Not affectedStated 7 May 2024 Firewall rules block traffic to public addresses outside the tunnel, so pushed routes cannot expose it. mullvad.net blogRead 18 Oct 2026
TunnelVisionCVE-2024-3661 Android Not affectedStated 7 May 2024 Android does not implement DHCP option 121, the route-pushing mechanism the attack needs. mullvad.net blogRead 18 Oct 2026
TunnelVisionCVE-2024-3661 iOS AffectedStated 7 May 2024 Mullvad said the fix is probably the same as for LocalNet. It has not said whether the 2026.2 "Force all apps" setting also covers TunnelVision. mullvad.net blogRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 Windows, macOS, Linux, Android Not affectedStated 9 Aug 2023 Traffic outside the tunnel is blocked; with local network sharing on, only reserved local ranges are allowed. mullvad.net blogRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 iOS MitigatedStated 21 Apr 2026Mitigation: the Force all apps setting, iOS 2026.2 Affected at disclosure. Version 2026.2 added a "Force all apps" setting that mitigates it; the setting has to be switched on. Changelog on GitHubRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 Windows, macOS, Linux, Android, iOS Not affectedStated 9 Aug 2023 The app gets server addresses from Mullvad's own API, not from DNS, so a spoofed DNS answer has nothing to change. mullvad.net blogRead 18 Oct 2026
Android leaks DNS outside the tunnel Android AffectedStated 3 May 2024 An Android bug, not Mullvad's app: DNS can leak when a VPN has no DNS server set and briefly while the tunnel is reconfigured or the app stops, even with 'Block connections without VPN' on. Mullvad said it would set a placeholder DNS server while blocking and that leaks during reconnects are harder to prevent. mullvad.netRead 10 Nov 2026

Latest app versions: Windows, macOS, Linux 2026.5 (11 Sep 2026); Android 2026.12 (30 Sep 2026); iOS 2026.5 (8 Sep 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 Mullvad, from its own statements or a primary document. Incidents across providers.

DateWhat happenedProvider’s responseSource
18 Apr 2023 Swedish police came to Mullvad's office with a search warrant for customer data and left without seizing anything. Mullvad said such customer data did not exist under its policies. mullvad.net blogRead 19 Oct 2026

Published audits

Audits and tests Mullvad 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
1 Jun 2026 Leviathan Security Apps Android app 2026.2 against the App Defense Alliance MASA profile; black-box, no code review. Not published Report mullvad.net blogRead 18 Oct 2026
6 Mar 2026 Assured Protocol GotaTun 0.2.0, Mullvad's WireGuard implementation; DAITA, the CLI and external dependencies excluded. 2 low Report mullvad.net blogRead 18 Oct 2026
21 Jan 2026 X41 D-Sec Backend and payments White-box review of the account and payment API and backend; some findings redacted. 3 medium, 2 low Report mullvad.net blogRead 18 Oct 2026
23 Oct 2025 Assured Backend and payments Penetration test of the customer web app. 1 low Report mullvad.net blogRead 18 Oct 2026
19 May 2025 Assured Apps The installer and downloader (VPN loader): protocol and source code. Not published Report mullvad.net blogRead 18 Oct 2026
27 Mar 2025 NCC Group Apps Android app 2024.9 against the MASA profile; black-box, no code reviewed. Not published Report mullvad.net blogRead 18 Oct 2026
11 Dec 2024 X41 D-Sec Apps Penetration test and source review of the VPN app on all platforms, October to November 2024. 3 high, 2 medium, 1 low Report mullvad.net blogRead 18 Oct 2026
27 Jun 2024 Cure53 Servers and infrastructure One OpenVPN and one WireGuard staging server plus the Ansible code, with a privacy focus. 1 medium, 1 low Report mullvad.net blogRead 18 Oct 2026
9 Aug 2023 Radically Open Security Servers and infrastructure Two RAM-only VPN servers, including a check for logging; binaries and hardware excluded. Not published mullvad.net blogReport not publicRead 18 Oct 2026
17 Feb 2023 Assured Backend and payments Account and payment API, tested in November 2022. None reported Report mullvad.net blogRead 18 Oct 2026
21 Oct 2022 Atredis Partners Apps Penetration test and source audit of the apps on five platforms. Not published Report mullvad.net blogRead 18 Oct 2026
14 Sep 2022 Assured Servers and infrastructure Self-hosted authoritative DNS servers, before they went into production. None reported Report mullvad.net blogRead 18 Oct 2026
22 Jun 2022 Assured No-logs Two WireGuard and one OpenVPN server, freshly installed: configuration and any customer logging. Not published Report mullvad.net blogRead 18 Oct 2026
20 Jan 2021 Cure53 Servers and infrastructure First infrastructure audit, December 2020; six issues from informational to high, no breakdown given. Not published Report mullvad.net blogRead 18 Oct 2026
25 Jun 2020 Cure53 Apps Desktop 2020.4, Android and iOS apps; the worst finding was rated medium. Not published Report mullvad.net blogRead 18 Oct 2026

Who runs Mullvad, and on what

Company
Mullvad VPN AB, Sweden. Part of Amagicom AB. Both companies are owned by the two founders. mullvad.netRead 18 Oct 2026
RAM-only servers
All VPN servers run from RAM without disks since September 2023. mullvad.net blogRead 19 Oct 2026
Infrastructure audit
Mullvad says its RAM-only infrastructure has been audited twice. mullvad.net blogRead 19 Oct 2026
Open-source apps
Desktop and mobile client source is public on GitHub (GPL-3.0). Code Changelog on GitHubRead 19 Oct 2026
Transparency, the April 2023 police search
No regular report or canary. Mullvad disclosed a police search in April 2023; officers left without customer data. mullvad.net blogRead 18 Oct 2026

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

Compare: Mullvad vs IVPN: owners, audits and leak history side by side; Mullvad vs Proton VPN: owners, audits and leak history side by side. All VPN provider comparisons.

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 Mullvad

  1. Before connecting, note the visible address, the ASN it belongs to, and whether IPv6 answers.
  2. Connect with the Mullvad app. There is no kill switch to enable; if you use Lockdown mode, note that it keeps blocking after you quit.
  3. Rerun the checks in the same browser and look at the ASN on the new address.
  4. The ASN should move to Mullvad's own AS39351, and IPv6 should follow whatever you set the IPv6 option to.
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

Mullvad leak test FAQ

Does Mullvad have a kill switch I need to switch on?

No. Mullvad documents the kill switch as always on and not disableable in settings, active from the moment you press Connect. Lockdown mode is a separate optional setting that also blocks the internet after you disconnect or quit.

Why does the IPv6 check return nothing on Mullvad?

On Windows and Linux, Mullvad treats IPv6 as an option you enable when you need it rather than a default. An empty IPv6 reading on those platforms usually reflects that setting. Mullvad advises Mac users to leave IPv6 enabled.

Should my exit address belong to AS39351?

Mullvad announces address space under its own AS39351, so a lookup on your exit address naming Mullvad is a strong confirmation the tunnel is carrying your traffic. Mullvad also uses colocation, so treat a different network as a question to investigate rather than proof of a leak.

Why is my DNS check not naming Mullvad?

A custom DNS server set in the app's advanced settings takes precedence and also overrides Mullvad's content blockers. Mullvad additionally documents that a public DNS server only works over WireGuard, so protocol choice can change the result.

Does Mullvad publish independent audits?

Yes. Mullvad publishes the reports on its own blog: X41 D-Sec audited the apps across platforms in late 2024, and Cure53 completed a fourth infrastructure audit in June 2024. Those are claims about Mullvad's code and servers, not about your browser session.

Why does my browser fingerprint look the same as before?

A VPN moves your network path; it does not rewrite the browser. Fingerprint and WebRTC signals are produced locally, which is the reason Mullvad ships a separate hardened browser rather than trying to fix them from the VPN app.