MyIPScan

Independent self-test

Private Internet Access Leak Test

Private Internet Access describes its network as IPv4 only and blocks IPv6 rather than carrying it, which is why an IPv6 leak test on PIA should normally come back empty. Two other things set it apart on these checks: its apps are published as open source, and its advanced kill switch keeps blocking traffic even when the app is not running. What you get back describes your session; it is not an audit of PIA.

Read methodology

Live test

Run the test on Private Internet Access now

Private Internet Access runs an IPv4-only network and blocks IPv6, so the IPv6 line below should normally come back empty.

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

Current-session checks

What this Private Internet Access self-test checks

Read each signal once on your ordinary connection and once connected. On PIA the two lines that repay attention are IPv6, which should go quiet, and the resolver, because MACE changes what DNS answers look like.

Before you read the result

What Private Internet Access documents about these signals

The points below are taken from PIA's own feature pages and help desk. They describe the behaviour a normal reading reflects.

An IPv4-only network that blocks IPv6

PIA describes its service as operating exclusively on IPv4 and lists aggressive IPv6 blocking as a feature, on the grounds that traffic it cannot carry should not be allowed out. An empty IPv6 result while connected is therefore the intended behaviour here, and an IPv6 address belonging to your own connection is the reading worth chasing.

MACE answers blocked domains at the DNS layer

PIA's MACE is a DNS-level blocker: when a domain is on its list, the resolver answers with 127.0.0.2, which points back at your own machine so the request never leaves. That is useful to know when reading a DNS check, because a loopback answer is MACE doing its job rather than a broken resolver.

The advanced kill switch outlives the app

PIA documents a kill switch that blocks traffic when the connection drops, and an advanced kill switch that blocks all traffic outside the VPN even when the VPN is turned off. Which of the two you have on decides whether anything could have escaped in the gap that a failed check is reporting.

Split Tunnel decides what was in the tunnel at all

PIA's desktop Split Tunnel lets you mark individual applications Bypass VPN so they connect directly, and exclude individual addresses or whole subnets. On Windows and Linux there is a further setting for whether DNS requests follow those rules or always use PIA's own DNS. A browser marked Bypass VPN will report your own address, correctly.

Open-source apps, browser-side signals

PIA publishes its applications as open source alongside the WireGuard and OpenVPN protocols they use, so the client behaviour behind these readings can be inspected rather than taken on trust. That does not extend to WebRTC or fingerprint values, which your browser generates locally and no VPN client rewrites.

Between the readings

Record a kill-switch drop on Private Internet Access

Private Internet Access documents a kill switch that blocks traffic when the connection drops, and an advanced one that keeps blocking even when the app is not running. The gap between those two behaviours is measured in seconds.

Known leak issues and fixes

How Private Internet Access 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, Android MitigatedStated 8 May 2024Mitigation: the kill switch, on by default PIA says the kill switch, on by default, protects every platform except iOS; the exploit needs it switched off. privateinternetaccess.com blogRead 18 Oct 2026
TunnelVisionCVE-2024-3661 iOS AffectedStated 8 May 2024 PIA says iOS can be affected because Apple controls how traffic is routed there. privateinternetaccess.com blogRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 All apps Not statedChecked 18 Oct 2026 No PIA statement found, and its changelog does not mention it. privateinternetaccess.comRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 18 Oct 2026 No PIA statement found, and its changelog does not mention it. privateinternetaccess.comRead 18 Oct 2026
IP leak with split tunnelling in bypass mode Linux FixedStated 7 Jul 2025Fix: 3.6.2 PIA's changelog: fixed a potential IP leak when split tunnelling runs in bypass mode. privateinternetaccess.comRead 18 Oct 2026

Latest app versions: Windows, macOS, Linux 3.8.0 (15 Oct 2026); Android 4.1.5 (20 Oct 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 Private Internet Access, from its own statements or a primary document. Incidents across providers.

DateWhat happenedProvider’s responseSource
Jul 2016 Russian authorities seized several Private Internet Access servers in July 2016, and PIA removed its servers from Russia. PIA said the seizure happened without due process or notification and that it would not comply with Russian censorship demands. privateinternetaccess.com blogRead 26 Oct 2026

Published audits

Audits and tests Private Internet Access 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
8 Dec 2025 Deloitte No-logs Deloitte Audit Romania, ISAE 3000: server configuration as of 31 October 2025, including dedicated-IP tokens. Not published Report privateinternetaccess.com blogRead 18 Oct 2026
25 Apr 2024 Deloitte No-logs Deloitte Audit Romania: servers, network and incident management, dedicated IP. Not published privateinternetaccess.com blogReport not publicRead 18 Oct 2026
30 Aug 2022 Deloitte No-logs Deloitte Audit Romania: server configuration as of 30 June 2022. Not published privateinternetaccess.com blogReport not publicRead 18 Oct 2026

Who runs Private Internet Access, and on what

Company
Private Internet Access, Inc., United States. Part of Kape Technologies since 2019. Kape lists the PIA acquisition as December 2019. privateinternetaccess.comRead 18 Oct 2026
Open-source apps
Desktop, iOS and browser-extension clients are published on GitHub. Code Changelog on GitHubRead 19 Oct 2026
RAM-only servers
PIA says its servers are RAM-only. privateinternetaccess.comRead 11 Nov 2026
Transparency, Apr-Jun 2026
19 requests. Subpoenas, warrants and foreign requests; PIA says it produced no logs. privateinternetaccess.com blogRead 18 Oct 2026

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

Compare: ExpressVPN vs Private Internet Access: 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 Private Internet Access

  1. Record the address, resolver and IPv6 result on your normal connection before you start.
  2. Connect with the PIA app and note whether you have the standard kill switch or the advanced one enabled.
  3. Rerun the same checks in the same browser, leaving MACE in whatever state you normally use it.
  4. IPv4 and the resolver should change, IPv6 should stop answering, and a 127.0.0.2 answer in a DNS result is MACE rather than a fault.
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

Private Internet Access leak test FAQ

Does Private Internet Access support IPv6?

PIA describes its network as IPv4 only and lists aggressive IPv6 blocking as a feature. An IPv6 check that returns nothing while connected is the expected outcome of that design.

Why did a DNS lookup return 127.0.0.2?

That is PIA's MACE feature. It filters at the DNS layer and answers blocked domains with 127.0.0.2, an address that points back at your own machine, so the request is never made.

What does the advanced kill switch do differently?

PIA describes the advanced kill switch as blocking all traffic outside the VPN even when the VPN is turned off, where the standard kill switch acts when a live connection drops.

My browser shows my real address even though PIA is connected.

Check Split Tunnel first. PIA lets you mark an application Bypass VPN so it connects directly, and on Windows and Linux there is a separate setting for whether DNS follows those rules. A browser on the bypass list is behaving as configured.

Are PIA's apps really open source?

PIA publishes its applications as open source, along with the WireGuard and OpenVPN protocols they build on. That makes the client side of these checks inspectable; it says nothing about what happens on the servers.

A check still shows my own address. Where do I look?

Confirm which kill switch is enabled, restart the browser so it drops cached connections, and rerun the focused DNS, WebRTC and IPv6 tools before drawing a conclusion from one reading.