MyIPScan

Independent self-test

NordVPN Leak Test

NordVPN handles IPv6 by shutting it down rather than carrying it: its own documentation describes blocking the IPv6 interface and rerouting IPv4 only. That single decision explains most of what an IPv6 leak test shows here. It also runs its own DNS servers, and it ships two different kill switches that behave differently. Treat the output as a description of your own session rather than an assessment of NordVPN.

Read methodology

Live test

Run the test on NordVPN now

NordVPN blocks the IPv6 interface rather than carrying it, and answers DNS from its own resolvers, so those are the two lines to read first.

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

Current-session checks

What this NordVPN self-test checks

Take one reading on your normal connection and one connected. On NordVPN the IPv6 result should go quiet by design, so the lines worth studying are the resolver that answered and what WebRTC exposed.

Before you read the result

What NordVPN documents about these signals

Each point below is taken from NordVPN's own blog and support articles. They set out what a normal reading is supposed to look like.

IPv6 is blocked, not tunnelled

NordVPN describes IPv6 leak protection as blocking the IPv6 interface so that only IPv4 traffic is rerouted and encrypted. An IPv6 check that returns nothing while you are connected is therefore the documented outcome. An IPv6 address that still resolves to your own connection is the reading that needs investigating.

Two kill switches that are not the same thing

NordVPN separates an internet kill switch from an App Kill Switch, which closes named applications when the connection drops. NordVPN's support pages state that the App Kill Switch is off by default on desktop, while on mobile the kill switch is enabled by default and is not exposed as its own setting. Knowing which one you have on changes how you read a failed check.

DNS answers come from NordVPN's resolvers

NordVPN operates its own DNS servers, and Threat Protection filters domains at that layer against reputation databases and phishing detection. NordVPN also notes that Threat Protection overrides a custom DNS setting, so if you pointed the app at a resolver of your own and the DNS check does not show it, that feature is the first thing to look at.

There is a published address to compare against

NordVPN documents its own DNS server addresses, 103.86.96.100 and 103.86.99.100, in its support material. That gives the DNS check on this page something concrete to be measured against: a resolver answering from those addresses is NordVPN's, and one answering from your ISP's range is not, without any need to infer it from the result.

What the app does not decide

WebRTC candidates and fingerprint values are produced by the browser. With the whole system routed through the app they should carry the tunnel address, but an extension, a virtual adapter or split tunnelling can change that. Nothing on this page inspects NordVPN's servers - only what your browser reveals in this session.

Between the readings

Record a kill-switch drop on NordVPN

NordVPN separates an internet kill switch from an App Kill Switch, and its support pages put the App Kill Switch off by default on desktop. Which of them was covering this browser shows up in the seconds after the tunnel address disappears.

Known leak issues and fixes

How NordVPN 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, Linux, Android Not affectedPage undated, read 18 Oct 2026 NordVPN says these apps were immune thanks to existing mitigations; on Windows and Linux the OS firewall keeps traffic in the tunnel. support.nordvpn.comRead 18 Oct 2026
TunnelVisionCVE-2024-3661 macOS, iOS MitigatedPage undated, read 18 Oct 2026Mitigation: the Stay invisible on a local network setting Affected by default. The setting also covers DHCP option 121 routes, but NordVPN says Apple bugs can break the app with it on (iOS 17 and later). support.nordvpn.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 Windows, Linux, Android Not affectedPage undated, read 18 Oct 2026 NordVPN says these apps were immune due to implemented mitigations. support.nordvpn.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 macOS, iOS MitigatedPage undated, read 18 Oct 2026Mitigation: the Stay invisible on a local network setting The setting was fully released by the beginning of August 2023 and has to be switched on. support.nordvpn.comRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 18 Oct 2026 NordVPN's article covers only the local network attack, not ServerIP. support.nordvpn.comRead 18 Oct 2026

Latest app versions: Linux 5.4.1 (13 Oct 2026); Windows 8.14 (23 Oct 2026); macOS 10.13 (16 Oct 2026); iOS 9.16 (19 Oct 2026); Android 9.15 (15 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 NordVPN, from its own statements or a primary document. Incidents across providers.

DateWhat happenedProvider’s responseSource
Oct 2024 NordVPN received a binding warrant from the Panamanian prosecutor's office in a criminal investigation. NordVPN said it could provide only payment data and confirmation that the account existed, because it keeps no traffic, connection or activity logs. nordvpn.com blogRead 26 Oct 2026
Mar 2018 One rented NordVPN server in a Finnish data centre was accessed by an intruder through a management account the data centre had left unsecured; NordVPN disclosed it on 21 October 2019. NordVPN said only that one server was affected, it held no user activity logs, and the stolen TLS keys could not decrypt VPN traffic. nordvpn.com blogRead 26 Oct 2026

Published audits

Audits and tests NordVPN 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
3 Feb 2026 Deloitte No-logs Sixth no-logs assurance engagement, 10 November to 12 December 2025. Not published nordvpn.com blogReport not publicRead 26 Oct 2026
10 Dec 2025 Cure53 Apps Pentest of all desktop and mobile apps, browser extensions, APIs and NordAccount login. 3 high, 4 medium, 15 low, 8 info sb.nordcdn.com reportRead 26 Oct 2026
10 Dec 2025 Cure53 Servers and infrastructure Pentest of VPN servers and supporting infrastructure, October 2025. 2 high, 1 medium, 4 low, 2 info sb.nordcdn.com reportRead 26 Oct 2026
18 Feb 2025 Deloitte No-logs Deloitte Audit Lithuania, fifth engagement, with access from 18 November to 20 December 2024. Not published nordsecurity.comReport not publicRead 18 Oct 2026
9 Jan 2024 Deloitte No-logs Fourth no-logs assurance engagement, 30 November to 7 December 2023: standard, Double VPN, obfuscated, Onion over VPN and P2P servers. Not published nordvpn.com blogReport not publicRead 26 Oct 2026
28 Feb 2023 Cure53 Apps Pentest and source code audit of the Windows, Linux and macOS apps, browser add-ons and related backend services. 1 critical, 2 high, 1 medium, 7 low, 11 info Report cure53.deRead 26 Oct 2026
28 Feb 2023 Cure53 Servers and infrastructure Pentest and source code audit of NordVPN servers and infrastructure. 1 high, 2 medium, 1 low, 7 info Report cure53.deRead 26 Oct 2026
10 Jan 2023 Deloitte No-logs Reasonable assurance on IT system configuration against the no-logs claim, 21 November to 10 December 2022. Not published sb.nordcdn.com reportRead 26 Oct 2026
1 Jul 2020 PwC No-logs Second assurance engagement on the no-logs claim, 20 to 28 May 2020, adding obfuscated, Double VPN and P2P servers. Not published nordvpn.com blogReport not publicRead 26 Oct 2026
10 Oct 2019 VerSprite Apps Penetration test of the NordVPN apps. Not published newswire.comReport not publicRead 26 Oct 2026
Nov 2018 PwC No-logs First assurance engagement on NordVPN's no-logs claim, ordered in late 2018. Not published nordvpn.com blogReport not publicRead 26 Oct 2026

Who runs NordVPN, and on what

Company
nordvpn S.A., Panama. Part of Nord Security. NordVPN's help centre says it operates under Panama's jurisdiction and that its parent, Nord Security, is based in the Netherlands; its founders and owners article names nordvpn S.A. support.nordvpn.comRead 26 Oct 2026
Open-source apps
The NordVPN Linux app is open source; the rest of the service is proprietary. Code support.nordvpn.comRead 19 Oct 2026
RAM-only servers
NordVPN says it chose diskless RAM servers instead of hard disk servers for its network. nordvpn.com blogRead 26 Oct 2026
Transparency, Jul-Sep 2026
79 requests. NordVPN publishes quarterly counts of government inquiries and DMCA requests: 79 government inquiries for July to September 2026. nordvpn.com blogRead 26 Oct 2026

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

Compare: NordVPN vs Surfshark: owners, audits and leak history side by side; ExpressVPN vs NordVPN: 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 NordVPN

  1. Before connecting, record the address, the resolver and whether IPv6 answers at all on your normal connection.
  2. Connect with the NordVPN app and check which kill switch is enabled, since the App Kill Switch and the internet kill switch are separate settings.
  3. Rerun the same checks in the same browser without changing profile or extensions.
  4. IPv4 and the resolver should change, and IPv6 should stop answering because the interface is blocked rather than tunnelled.
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

NordVPN leak test FAQ

Does NordVPN support IPv6?

NordVPN documents IPv6 leak protection as blocking the IPv6 interface and rerouting IPv4 only. An empty IPv6 result on this page is therefore the expected reading rather than a sign the test failed.

Which kill switch does NordVPN turn on by default?

NordVPN's support pages state that the App Kill Switch is off by default on desktop, while on mobile the kill switch is enabled by default and is not shown as a separate option in settings.

Which DNS addresses belong to NordVPN?

NordVPN publishes 103.86.96.100 and 103.86.99.100 as its own DNS servers in its support material, which gives you a fixed reference to compare the resolver in your result against.

Why does the DNS check not show the custom resolver I set?

NordVPN notes that Threat Protection overrides a custom DNS setting because the filtering happens on NordVPN's own DNS servers. Turning that feature off is the usual reason a custom resolver reappears.

Can this page tell me whether NordVPN keeps logs?

No. These checks read what your browser exposes in one session. Logging happens on the provider's side and cannot be observed from a browser test, whatever the result looks like.

A check still shows my own address. What should I look at?

Confirm the app is connected and the kill switch you rely on is the one that is enabled, restart the browser to drop cached connections, then rerun the focused DNS, WebRTC and IPv6 tools.