---
title: "WebRTC Leak Test: Does Your Browser Leak Your Real IP?"
description: "Free WebRTC leak test: compares the IP WebRTC reveals with the IP sites see, flags raw local IPs and time zone mismatches, with Chrome and Firefox fixes."
canonical: "https://browser-use.com/tools/webrtc-leak-test"
last_updated: "2026-11-03"
---

# WebRTC Leak Test: Does Your Browser Leak Your Real IP?

## WebRTC Leak Test

Checks whether WebRTC shows sites a different IP than your proxy or VPN, and whether your browser time zone matches your IP location.

## How it works

### Open the page

The test runs on its own: your browser asks a STUN server for its address, and this site returns the IP it sees.

### Read each row

Each row shows a verdict, the raw value and why. Using a proxy or VPN? Tick the box so a different IP counts as a leak.

### Fix and run again

Apply a fix below, restart the browser and press Run again. Copy JSON gives agents and CI the same result.

### How do I stop WebRTC leaks in Chrome?

Set the WebRtcIPHandling policy, or the profile preference webrtc.ip\_handling\_policy, to disable\_non\_proxied\_udp. WebRTC then uses TCP, and UDP only through a proxy that supports it. The --force-webrtc-ip-handling-policy flag only works in chrome-headless-shell; Chrome ignores it.

Source: [Chromium WebRtcIPHandling policy](https://github.com/chromium/chromium/blob/main/components/policy/resources/templates/policy_definitions/WebRtc/WebRtcIPHandling.yaml) · [Chromium pref\_names.h](https://github.com/chromium/chromium/blob/main/chrome/common/pref_names.h) · [Chromium headless\_web\_contents\_impl.cc](https://github.com/chromium/chromium/blob/main/headless/lib/browser/headless_web_contents_impl.cc)

### How do I stop WebRTC leaks in Firefox?

In about:config, set media.peerconnection.ice.proxy\_only\_if\_behind\_proxy to true to keep WebRTC on your proxy, or media.peerconnection.enabled to false to turn WebRTC off.

Source: [Firefox all.js](https://github.com/mozilla-firefox/firefox/blob/main/modules/libpref/init/all.js) · [Firefox StaticPrefList.yaml](https://github.com/mozilla-firefox/firefox/blob/main/modules/libpref/init/StaticPrefList.yaml)

### Is a .local address a leak?

No. Browsers can hide local IPs behind random names ending in .local (mDNS). A raw address such as 192.168.1.20 means that protection is off and any page can read it. It is not your public IP.

Source: [IETF mDNS ICE candidates draft](https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-mdns-ice-candidates)

## Automating behind a proxy?

Browser Use cloud browsers are Chromium with residential proxies and CAPTCHA solving, built for AI agents and scrapers.

[See stealth browsers](https://browser-use.com/stealth-browsers)

## What this test sends

-   WebRTC candidates and the comparison stay in this tab.
-   One request to this site, which returns the IP it already sees. Our code does not log or store it.
-   STUN requests to [Cloudflare's public STUN server](https://developers.cloudflare.com/realtime/turn/), so Cloudflare sees your IP.
-   The site's usual analytics records that the test ran, not the result.

---

BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)