PrivadoVPN Leak Test: IP, DNS, WebRTC, IPv6

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

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.

Run the VPN Leak Test Review IP, DNS, WebRTC, IPv6 and browser/session signals together. Check DNS signals Review limited resolver-signal behavior for this browser session. Review WebRTC exposure Check browser WebRTC candidate behavior. Check IPv6 visibility Review whether IPv6 appears in visible signals. Review browser fingerprint Check browser characteristics a VPN usually does not change. Read the methodology Review the limits before interpreting results.

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.

Open the drop recorder

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

On your normal connection, note the visible address, which resolver answered, and whether the IPv6 check returned anything at all.
Open the PrivadoVPN app, switch the Kill Switch on, and connect to a location you can remember.
Rerun the same checks in the same browser and the same profile, so the two readings are comparable.
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.

Other provider self-tests

The same current-session checks, walked through for another provider. Listed alphabetically; this is not a ranking or a comparison.

All provider self-testsIndex of every provider walkthrough on MyIPScan.Perfect Privacy leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.Private Internet Access leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.Proton VPN leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.Psiphon leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.