MyIPScan

Independent self-test

hide.me Leak Test

hide.me is one of the few providers here that carries IPv6 rather than switching it off, and that changes how you read an IPv6 leak test: an IPv6 address in the result is not automatically a problem. Its own Linux client documents IPv6 tunnelling, a default set of hide.me resolvers, and leak protection built on the routing subsystem rather than a simple on-off toggle. Anything you see here describes your own session rather than hide.me's infrastructure.

Read methodology

Live test

Run the test on hide.me now

hide.me tunnels IPv6 rather than switching it off, so an IPv6 address below is not automatically a fault. Compare it against the visible IPv4 line.

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

Current-session checks

What this hide.me self-test checks

Read the signals once before connecting and once after. On hide.me the IPv6 line needs the most care, because an address there may mean the tunnel is carrying IPv6 exactly as documented.

Before you read the result

What hide.me documents about these signals

The points below come from hide.me's own published client documentation, which is unusually specific about how leak protection is implemented.

IPv6 is tunnelled, not blocked

hide.me's published Linux client lists IPv6 support among its features and exposes an option to use IPv6 tunnelling only, and it documents the server as providing both IPv4 and IPv6 addressing on connect. So an IPv6 address in your result may be the tunnel working. The question to ask is whose network that address belongs to, not whether it exists.

Compare the two families against each other

Because both address families can be live at once, the useful comparison on hide.me is between them. If the IPv4 exit and the IPv6 address point at the same provider network, that is consistent with a dual-stack tunnel. If the IPv6 address belongs to your own ISP while IPv4 does not, that is the mismatch worth acting on.

Resolvers are set by the client

hide.me's client ships with its own DNS servers configured as the default for client requests rather than deferring to whatever the network hands out. A DNS check while connected should therefore stop naming your ISP's resolver. Which resolver actually answered is exactly what the DNS tool on this page reports.

Leak protection built on routing

hide.me describes its leak protection, the equivalent of a kill switch, as based on the routing subsystem: it installs a dedicated routing table and policy rules so that traffic is selectively routed rather than merely blocked after a drop. A check that shows your own address is a prompt to look at that configuration rather than at the browser.

The client is published as source

hide.me publishes its Linux client as source code, which is how the details above can be read rather than taken on trust: the resolver defaults, the IPv6-only tunnelling option and the routing-table approach to leak protection are all visible in the repository. What happens on the server side stays outside both the source and this page.

Between the readings

Record a kill-switch drop on hide.me

The checks above read one instant of a hide.me session. A reconnect is a stretch of seconds, and whether your own address surfaced somewhere inside it is a different question from what any single reading returns.

Known leak issues and fixes

How hide.me 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 MitigatedStated 4 Jun 2024Mitigation: the Kill Switch, on by default only on Linux hide.me points to its kill switch, which limits traffic to its VPN servers. hide.me blogRead 18 Oct 2026
TunnelVisionCVE-2024-3661 Android Not affectedStated 4 Jun 2024 A statement about Android itself rather than the hide.me app. hide.me blogRead 18 Oct 2026
TunnelVisionCVE-2024-3661 iOS AffectedStated 4 Jun 2024 A statement about iPhones and iPads in general; hide.me cites App Store limits on kill switches. hide.me blogRead 18 Oct 2026
TunnelCrack LocalNetCVE-2023-36672, CVE-2023-35838 All apps Not statedChecked 28 Jun 2024 hide.me's post on VPN vulnerabilities does not mention TunnelCrack. hide.me blogRead 18 Oct 2026
TunnelCrack ServerIPCVE-2023-36673, CVE-2023-36671 All apps Not statedChecked 28 Jun 2024 hide.me's post on VPN vulnerabilities does not mention TunnelCrack. hide.me blogRead 18 Oct 2026

Latest app versions: Linux 0.9.14 (7 Sep 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 hide.me 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
7 Jun 2024 Securitum No-logs VPN container image, configuration files, deployment process and staff interviews against the no-logs claim, as of March 2024. Not published Report hide.meRead 18 Oct 2026

Who runs hide.me, and on what

Company
eVenture Limited, Malaysia. Registered office in Labuan. hide.meRead 18 Oct 2026
Open-source apps
hide.me's Linux command-line client is open source (GPL-2.0). Code Changelog on GitHubRead 19 Oct 2026
Transparency, 2025
9 requests. Law enforcement requests in 2025, alongside abuse complaints and DMCA notices; hide.me says it handed over no data. hide.me reportRead 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 hide.me

  1. Note the IPv4 address, the resolver and any IPv6 address on your normal connection first.
  2. Connect with hide.me and leave IPv6 enabled on the device rather than disabling it, since the tunnel is documented as carrying it.
  3. Rerun the same checks in the same browser.
  4. Compare the two address families against each other. Both should point at the provider network; an IPv6 address still tied to your ISP is the mismatch to fix.
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

hide.me leak test FAQ

Does hide.me support IPv6?

hide.me's published client documentation lists IPv6 support and an IPv6-only tunnelling option, and describes the server as providing both IPv4 and IPv6 addressing. IPv6 is carried rather than switched off.

Is an IPv6 address in the result a leak?

Not on its own. Because hide.me tunnels IPv6, the meaningful test is whether the IPv6 address belongs to the provider network or to your own connection. A match with the IPv4 exit is the reassuring case.

Which DNS servers answer while I am connected?

hide.me's client sets its own DNS servers as the default for client requests rather than using whatever the local network supplies. The DNS check on this page reports which resolver actually answered for your browser.

Does hide.me have a kill switch?

hide.me documents leak protection built on the routing subsystem, using a dedicated routing table and policy rules to control which traffic can leave, rather than a simple block-after-drop switch.

Can I verify any of this myself?

Some of it. hide.me publishes its Linux client as source, so the resolver defaults, the IPv6 tunnelling option and the routing rules are readable. Server behaviour is not, which is the gap a browser check like this one partly fills.

Why do the fingerprint values look unchanged?

A VPN changes the network path, not the browser. Screen metrics, fonts, language and similar values are reported by the browser itself, so they normally read the same before and after connecting.