MyIPScan

Provider-neutral self-test pilot

F-Secure VPN Leak Test

By: · Updated August 2026

F-Secure is unusually direct about one of the four signals on this page. Its user guide carries a topic titled F-Secure VPN and WebRTC IP address leakage, which states that the app cannot prevent IP address leaking through WebRTC and explains that the API lives inside the browser rather than in the tunnel. The product is the former FREEDOME VPN under a new name, and F-Secure's own help pages still sit under the freedome path, so an app still labelled FREEDOME is the same product. F-Secure lists Kill Switch for Windows, Mac and Android while also supporting iOS, which decides whether that setting exists for you to check at all. What follows describes your session, not F-Secure's servers.

Read methodology

Live test

Run the test on F-Secure VPN now

Read the WebRTC line before the others. F-Secure's user guide carries a topic stating that the app cannot prevent IP address leaking through WebRTC, and points at the browser rather than the app.

Open the full VPN Leak Test

Current-session checks

What this F-Secure VPN self-test checks

Take each reading once before connecting and once after, in the same browser. On F-Secure the WebRTC result is the one to weigh first, because the provider has already published what its app can and cannot do about it.

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 F-Secure VPN documents about these signals

The points below come from F-Secure's own product page for F-Secure VPN and from its user guide. They are limited to what the company itself publishes, which on protocols and resolvers is less than you might expect.

WebRTC is documented as out of the app's reach

F-Secure's user guide carries a topic on F-Secure VPN and WebRTC IP address leakage which states that the app cannot prevent IP address leaking through WebRTC. Its explanation is that WebRTC is a JavaScript API provided by the browser: code from a web server asks the browser for its addresses, and the browser answers, which is not something a tunnel sits in front of. The remedy F-Secure points to is a browser setting rather than an app setting. A WebRTC reading here is therefore a statement about your browser.

The switch is listed for three platforms, not four

F-Secure lists Kill Switch as available on Windows, Mac and Android, and describes it as preventing accidental leakage of your data to the internet if you momentarily lose your VPN connection. Its supported platforms also include iOS, which is the case where an unexpected reading cannot be traced back to that setting because there is none to check. The published requirements are Windows 11 or Windows 10 version 21H2 and later, macOS 13 and later, iOS 18 and later, and Android 11 and later.

The name changed and the documentation did not

F-Secure states that FREEDOME VPN is now F-Secure VPN, and that an app still called FREEDOME VPN is still the same protection. Its own user guide pages continue to sit under the freedome path, which is why a search for documentation can land you on a page carrying the older name. If you are checking a build labelled FREEDOME against this page, you are looking at the same product under its previous branding.

The transport is adjustable but not published

F-Secure says only that advanced users may also change the VPN protocol from the settings. It does not publish which protocols it offers on which platform, so the transport carrying this session is something the app can tell you and this page cannot. If two readings taken on different machines disagree, the protocol setting in each app is worth comparing before anything else is.

The location list is the reference point

F-Secure offers virtual locations in over 20 countries, with more than one location inside some of them. Geolocation databases map addresses on their own schedule and are neither complete nor always current, so a country reported by a lookup is a guess about an address rather than a fact about a route. Compare the reading against the location you picked in the app, rather than the other way round.

Between the readings

Record a kill-switch drop on F-Secure VPN

F-Secure lists Kill Switch for Windows, Mac and Android, and describes it as preventing accidental leakage of your data to the internet if you momentarily lose your VPN connection. Whether it caught a real drop on your device, and how long the gap lasted, is what a recording adds to a single reading.

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 F-Secure VPN

  1. Note the visible address, the resolver and the WebRTC result on your normal connection first.
  2. Open F-Secure VPN, choose a virtual location and connect, leaving the browser and its profile exactly as they were.
  3. Rerun the same checks and read the WebRTC line before any of the others.
  4. Expect the address to change. If WebRTC still reports an address of your own, F-Secure's documented position is that the fix belongs in the browser, not in the app.
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

F-Secure VPN leak test FAQ

Does F-Secure VPN stop WebRTC from revealing my IP address?

F-Secure states in its own user guide that it cannot prevent IP address leaking through WebRTC, and explains that WebRTC is a JavaScript API provided by the browser. Its documented remedy is a change inside the browser itself.

Where does F-Secure say the WebRTC fix belongs?

In the browser rather than the app. F-Secure's position, stated by its own staff, is that the leak is real, that a VPN cannot technically defeat it, and that it has to be addressed inside the web browser. It puts forward no app setting of its own as an answer to WebRTC.

Is there a kill switch to check on my iPhone?

F-Secure lists Kill Switch for Windows, Mac and Android, while its supported platforms also include iOS. On an iPhone there is no such setting to confirm when a reading looks unexpected.

My app is still called FREEDOME. Is this the same product?

Yes. F-Secure states that FREEDOME VPN is now F-Secure VPN and that an app still carrying the FREEDOME name gives you the same protection. Its user guide pages still sit under the freedome path for the same reason.

Which protocol is carrying my session?

F-Secure publishes only that advanced users may also change the VPN protocol from the settings. It does not list which protocols are offered on which platform, so the app itself is the place to read that off.

A lookup puts me in a different country from the one I picked. What now?

F-Secure offers virtual locations in over 20 countries. Geolocation databases map addresses independently and are not complete, so compare the result against the location you selected in the app rather than against where you are sitting.

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.Edge Secure Network leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.ExpressVPN leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.hide.me leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.Hola VPN leak testThe same IP, DNS, WebRTC and IPv6 checks, walked through here.