Connection privacy

Free IP, DNS & WebRTC Leak Test

Compare your public IP, WebRTC addresses and available DNS observations before and after connecting a VPN.

  • Public IP comparison
  • WebRTC observations
  • Optional baseline
Your check starts here

Observe connection addresses

Observe your browser’s public IP, WebRTC candidate addresses, and DNS resolver queries where the probe is available. Compare your address before and after connecting a VPN.

Optional: disconnect your VPN, save a baseline, reconnect, then run.

Start here

How to use this tool

Follow these steps to get observations you can interpret and act on.

  1. Save your normal address

    With your VPN disconnected, save a baseline if you want a before-and-after comparison. The baseline stays in this page session.

  2. Connect your VPN

    Wait for your VPN client to show a connected state, then run the address observations.

  3. Compare each source

    Review the public address, WebRTC candidates and available DNS observations separately. Recheck unexpected public addresses in your VPN settings.

Behind the check

How the IP leak test works

This IP leak checker separates the address seen by the website from addresses exposed through WebRTC. Comparing both with your normal connection helps you investigate traffic that may be taking an unexpected route.

A changed address or multiple DNS resolvers alone does not prove a leak. Failed or restricted tests stay inconclusive rather than receiving a privacy score.

Understanding your results

  • A different public address shows that this request used a different exit address; it does not verify every application on your device.
  • A private or local WebRTC candidate is not automatically a public IP leak. Compare public candidates with your baseline.
  • DNS resolver observations require the site’s authoritative DNS probe. An unavailable DNS check is inconclusive.
Know the scope

Privacy & important limitations

  • WebRTC sends a STUN request to the configured server, Google’s public STUN service by default. No camera or microphone permission is requested.
  • Your connection address is visible to this site. A changed IP or several DNS resolvers alone cannot establish that a VPN is safe or leaking.
Interpret the evidence

Measured findings include their source and scope. An unavailable check is never counted as a pass, a threat or a score.

Common questions

Frequently asked questions

Does a changed IP mean my VPN has no leaks?

It confirms a change for the observed request. Other applications, IPv6 traffic and DNS routes may behave differently, so check each relevant signal.

Why is the DNS result unavailable?

Resolver detection needs a working authoritative probe. The tool reports missing coverage explicitly instead of treating it as a successful leak test.