MyIPScan

Independent self-test

Surfshark Leak Test

Surfshark's support pages say plainly that the service does not support the IPv6 protocol, and they recommend disabling IPv6 on the device. That is the single most useful thing to know before reading an IPv6 leak test here, because an empty IPv6 result is the design rather than a fault. The result describes the device in front of you, not Surfshark's network.

Read methodology

Live test

Run the test on Surfshark now

Surfshark does not support IPv6 and recommends disabling it, so an empty IPv6 line is the design. The visible address also rotates by default.

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

Current-session checks

What this Surfshark self-test checks

Read each signal once unconnected and once connected. On Surfshark the IPv6 line is the one people misread most often, so start there and then compare the resolver and the WebRTC result.

Before you read the result

What Surfshark documents about these signals

Surfshark states each of the points below on its own support and feature pages, and together they explain most of what you will see.

IPv6 is unsupported by design

Surfshark's support pages state that at the moment Surfshark does not support the IPv6 protocol, and they publish instructions for turning IPv6 off on Windows, macOS, Linux and Android. If your IPv6 check comes back empty while connected, that matches what Surfshark documents. An IPv6 address that still resolves to your home connection is the case to act on.

Rotating IP changes the address under you

Surfshark's Rotating IP changes your address roughly every five minutes within the location you chose, without dropping the connection, and it does not apply to Dedicated IP, Static IP or MultiHop servers. If two runs a few minutes apart report different addresses, that feature is the likely explanation rather than an unstable tunnel.

DNS requests travel inside the tunnel

Surfshark describes routing DNS requests through its own encrypted tunnels so that a Wi-Fi operator or ISP cannot read them. A DNS check while connected should therefore stop showing your ISP's resolver. CleanWeb adds ad, tracker and malware blocking on top of that, which can also explain a page that refuses to load.

The kill switch is the setting behind a failed check

Surfshark describes its kill switch as cutting the internet automatically if the VPN connection drops. When a check returns your own address, the sequence worth reconstructing is whether the tunnel dropped and whether the kill switch was enabled at that moment, rather than whether the test itself misfired.

Audits cover the provider, not your browser

Surfshark publishes independent assurance work on its no-logs claim: Deloitte produced assurance reports in 2023 and again in 2025, and Cure53 has reviewed its server infrastructure. Those are statements about Surfshark's systems. The WebRTC and fingerprint readings on this page are produced by your browser and are unaffected by them.

Between the readings

Record a kill-switch drop on Surfshark

Surfshark describes a kill switch that cuts the internet automatically if the VPN connection drops. The interesting quantity sits between “drops” and “cuts”, and it is counted in seconds rather than settings.

Known leak issues and fixes

How Surfshark 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 affectedStated 5 Jun 2026 Surfshark says these apps are immune: firewall rules stop traffic leaving the device outside the tunnel. support.surfshark.comRead 18 Oct 2026
TunnelVisionCVE-2024-3661 macOS, iOS MitigatedStated 5 Jun 2026Mitigation: the Invisible on LAN setting Apple platforms rely on the Invisible on LAN setting, and Surfshark lists Apple VPN bugs that can break connectivity while it is on. support.surfshark.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 Windows, Linux, Android Not affectedStated 5 Jun 2026 Covered by the same article: the firewall keeps local-network tricks from pulling traffic out of the tunnel. support.surfshark.comRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 macOS, iOS MitigatedStated 5 Jun 2026Mitigation: the Invisible on LAN setting Mitigated by Invisible on LAN, which limits local network access; it carries the same Apple bugs. support.surfshark.comRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 5 Jun 2026 Surfshark's article on these attacks does not address ServerIP. support.surfshark.comRead 18 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.

Published audits

Audits and tests Surfshark 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
Mar 2026 Cure53 Protocol Architecture and cryptography of the Dausos protocol; only a summary is published. Not published surfshark.comReport not publicRead 18 Oct 2026
23 Jan 2026 SecuRing Servers and infrastructure Black-box penetration test of the network infrastructure, 1 to 10 December 2025. 1 medium Report surfshark.com blogRead 18 Oct 2026
16 Jun 2025 Deloitte No-logs ISAE 3000: standard, static and multiport servers and their deployment. Not published surfshark.com blogReport not publicRead 18 Oct 2026
9 Jun 2025 SecuRing Apps Web, desktop and mobile apps and extensions, February to April 2025; only an attestation letter is published. Not published surfshark.comReport not publicRead 18 Oct 2026
25 Jan 2023 Deloitte No-logs Server configuration and deployment, API, network software and staff interviews. Not published surfshark.com blogReport not publicRead 18 Oct 2026
Apr 2021 Cure53 Servers and infrastructure Servers, VPN configuration and related infrastructure; only a management summary is published. Not published surfshark.comReport not publicRead 18 Oct 2026
20 Nov 2018 Cure53 Browser extension Pentest and code audit of the Chrome and Firefox extensions. 1 low, 1 info Report surfshark.com blogRead 26 Oct 2026

Who runs Surfshark, and on what

Company
Surfshark B.V., Netherlands. Part of Nord Security. Common holding with Nord Security since 2022; Surfshark says it operates independently. surfshark.comRead 18 Oct 2026
RAM-only servers
Surfshark says its servers are RAM-only and wiped on every reboot. surfshark.comRead 19 Oct 2026
Transparency, Jul-Sep 2026
23 requests. Inquiries from government institutions; Surfshark replaced its warrant canary with this quarterly report. surfshark.comRead 18 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. 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 Surfshark

  1. On your normal connection, note the address, the resolver, and whether IPv6 answers at all.
  2. Connect with the Surfshark app and confirm the kill switch is enabled before you retest.
  3. Rerun the same checks in the same browser, with the same extensions loaded.
  4. Expect the address and resolver to change and IPv6 to stay quiet. If you have Rotating IP on, expect the address itself to keep moving.
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

Surfshark leak test FAQ

Does Surfshark support IPv6?

Surfshark's support pages state that at the moment it does not support the IPv6 protocol, and they recommend disabling IPv6 on your device. An empty IPv6 result on this page is consistent with that.

My IPv6 test shows an address from my own ISP. What does that mean?

Because Surfshark does not carry IPv6, an IPv6 address belonging to your own connection is the reading worth acting on. Surfshark publishes per-platform instructions for turning IPv6 off, which is its documented answer to this.

Why did my address change between two runs?

Surfshark's Rotating IP changes your address roughly every five minutes within the location you selected, without disconnecting. It does not apply on Dedicated IP, Static IP or MultiHop servers.

Does Surfshark run the DNS that answers my queries?

Surfshark describes routing DNS requests through its own encrypted tunnels rather than leaving them with your ISP. The DNS check here reports which resolver actually answered for your browser session.

Has Surfshark's no-logs claim been checked by anyone?

Surfshark publishes independent assurance reports from Deloitte covering its no-logs policy, in 2023 and again in 2025, and Cure53 has reviewed its server infrastructure. Those reports concern Surfshark's systems, not your session.

Why has my browser fingerprint not changed?

A VPN changes the network path, not the browser. Fonts, screen metrics, language and similar values are reported by the browser itself, so they usually look the same before and after connecting.

See also: On a Fire TV Stick: Firestick VPN leak test, run in the Silk browser with the VPN connected.