MyIPScan

Independent self-test

PrivadoVPN Leak Test

PrivadoVPN's own pfSense setup article states that its VPN does not currently support IPv6, and instructs you to set the IPv6 Configuration Type to None on the WAN interface when all firewall traffic is passed through the tunnel. The support centre repeats that instruction as standalone guides for Windows 11 and for Mac. The second fact that changes a reading is DNS: Privado says that instead of using your ISP's servers you use one of its own encrypted ones, and its published router configuration hands the VPN interface the address 198.18.0.1. The third is scope, because PrivadoVPN ships a browser extension alongside its full apps, and documents the extension as covering only the browser profile it is installed in. Everything below describes your own session rather than PrivadoVPN's servers.

Read methodology

Live test

Run the test on PrivadoVPN now

PrivadoVPN states that its VPN does not currently support IPv6, so an empty IPv6 line below is the documented behaviour. Read the resolver next, because Privado says you use one of its own encrypted DNS servers rather than your ISP's.

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

Current-session checks

What this PrivadoVPN self-test checks

Take each reading twice, once on your normal connection and once connected. On PrivadoVPN the IPv6 line and the resolver carry the most information, because both follow from choices Privado has published.

Before you read the result

What PrivadoVPN documents about these signals

The points below are drawn from PrivadoVPN's own support articles and feature pages. Knowing the intended behaviour is what separates an ordinary reading from one worth chasing.

IPv6 is not currently carried

PrivadoVPN's pfSense setup article states that its VPN does not currently support IPv6, and instructs you to set the IPv6 Configuration Type to None on the WAN interface when the whole firewall is routed through the tunnel. The support centre carries the same instruction as separate articles for Windows 11 and for Mac. An IPv6 check returning nothing while you are connected matches that design, and an IPv6 address that still belongs to your own network is the case those articles were written for.

DNS is answered by Privado resolvers

PrivadoVPN describes DNS leak prevention in its own words: instead of using your ISP's servers, you use one of its encrypted ones. Its published pfSense configuration is concrete about it, giving the VPN interface the address 198.18.0.1 as Privado's DNS server, while the WAN interface keeps a public resolver only so the tunnel can be established in the first place. A DNS check taken while connected should therefore name Privado infrastructure, and your ISP appearing there is the reading to look at twice.

The kill switch is a toggle you turn on

PrivadoVPN documents the kill switch as automatically shutting down your internet connection if the VPN connection is lost, so your real IP address is not exposed. Its Windows article tells you to switch it on rather than describing it as already active, and recommends enabling Auto Start under Settings and Application, and Auto Connect under Settings and VPN, so the machine is not left with its internet cut and no tunnel to restore. When a check returns an address you did not expect, that toggle is the first setting to confirm.

The extension stops at the browser profile

PrivadoVPN ships a Web Proxy Extension for Chromium browsers including Chrome, Edge, Brave, Opera and Vivaldi, and for Firefox, and documents that it protects browsing only for the profile where it is installed. For complete coverage across all apps on a desktop or mobile device, Privado points to its respective full apps. That is why a reading taken in the extension's browser can differ from one taken in a second browser on the same machine, and why neither reading contradicts the other.

SOCKS5 is configured inside one application

PrivadoVPN publishes SOCKS5 setup guides for download clients including qBittorrent, Deluge, uTorrent and Vuze, each of them entering a server address taken from your account panel and port 1080 into that one application's own connection settings. Nothing in those articles reaches the browser. If a SOCKS5 client is all you have configured, an IP check on this page showing your own address is that product behaving as documented.

Between the readings

Record a kill-switch drop on PrivadoVPN

PrivadoVPN describes its kill switch as automatically shutting down your internet connection if the VPN connection is lost, and its Windows article pairs that toggle with Auto Start and Auto Connect. A single reading cannot tell you how many seconds passed before any of it took effect.

Known leak issues and fixes

How PrivadoVPN 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 18 Oct 2026 No statement found in PrivadoVPN's version logs, support centre or blog. blog.privadovpn.com blogRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 All apps Not statedChecked 18 Oct 2026 No statement found in PrivadoVPN's version logs, support centre or blog. blog.privadovpn.com blogRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 18 Oct 2026 No statement found in PrivadoVPN's version logs, support centre or blog. blog.privadovpn.com blogRead 18 Oct 2026
macOS IPv6 issue patched macOS FixedStated 22 Sep 2022Fix: macOS 3.1.0 The version log calls it an IPv6 issue and does not say whether traffic leaked. blog.privadovpn.com blogRead 18 Oct 2026
macOS Kill Switch failed after an Ethernet reboot macOS FixedStated 8 Nov 2023Fix: macOS 3.7.0 Kill Switch bug fix in the macOS version log. blog.privadovpn.com blogRead 18 Oct 2026

Latest app versions: Windows 4.1.0 (19 May 2026); macOS 4.2.0 (10 Jul 2026); Android 4.0.11 (21 Apr 2026); iOS 3.12.3 (21 May 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.

Published audits

No published independent audit found as of 19 Oct 2026. The about page, homepage and a blog search for 'audit' mention no independent audit. privadovpn.comChecked 19 Oct 2026 All published VPN audits we track.

Who runs PrivadoVPN, and on what

Company
Privado Networks ehf, Iceland. The terms name the Icelandic company. privadovpn.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 PrivadoVPN

  1. On your normal connection, note the visible address, which resolver answered, and whether the IPv6 check returned anything at all.
  2. Open the PrivadoVPN app, switch the Kill Switch on, and connect to a location you can remember.
  3. Rerun the same checks in the same browser and the same profile, so the two readings are comparable.
  4. Expect the address and the resolver to change and the IPv6 line to stay empty. If only the browser extension or a SOCKS5 client is configured, the scope of the change is narrower by design.
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

PrivadoVPN leak test FAQ

Does PrivadoVPN support IPv6?

PrivadoVPN's own pfSense setup article states that its VPN does not currently support IPv6, and the support centre publishes separate guides for disabling IPv6 on Windows 11 and on Mac. An empty IPv6 result while connected is consistent with that.

The IPv6 check still returns an address. What does PrivadoVPN suggest?

Its documented answer is to switch IPv6 off at the device or the interface. The support centre has an article for Windows 11 and one for Mac, and the pfSense guide sets the IPv6 Configuration Type to None on the WAN interface. Rerun the IPv6 tool after applying the change for your platform.

Which DNS servers should answer while PrivadoVPN is connected?

PrivadoVPN says that instead of using your ISP's servers you use one of its own encrypted ones, and its pfSense guide assigns 198.18.0.1 to the VPN interface as its DNS server. The DNS check on this page reports which resolver actually answered for your session.

Is the PrivadoVPN kill switch on by default?

PrivadoVPN does not state a default. Its Windows article walks you through switching the Kill Switch on, and recommends pairing it with Auto Start and Auto Connect so a device is not left with no internet and no tunnel. Treat it as a setting to confirm rather than one to assume.

I installed the browser extension and another browser still shows my own address. Why?

PrivadoVPN documents the Web Proxy Extension as protecting browsing only for the profile where it is installed, and points to the full apps for coverage across all apps on a device. A second browser reporting your own address is that boundary rather than a fault.

Can this page confirm PrivadoVPN's no-log policy?

No. PrivadoVPN describes itself as a no-log VPN based in Switzerland, which is a statement about what the company stores. These checks read only what your own browser exposes during a single session.