Free WebRTC Leak Test | Check Browser IP Leaks

Your connection (HTTP)

Detected public IP: Detecting…
ISP: —
Country / City: —
Browser: Detecting…

WebRTC API support

RTCPeerConnection: —
RTCDataChannel: —
Media Devices API: —
Test status: Queued

WebRTC leak verdict

Running test…

Collecting ICE candidates from your browser.

How to fix a WebRTC leak

Your connection (WebRTC)

Detected public IP —

Local LAN IP —

Public IPv6 —

mDNS candidate —

Session Description (SDP)

Waiting for WebRTC offer…

Media Devices

Audio permission: —
Video permission: —
Audio inputs: —
Audio outputs: —
Video inputs: —

A WebRTC leak happens when your browser exposes your real IP through WebRTC candidates, even while your HTTP traffic uses a VPN or proxy.

WebRTC is a browser technology that allows direct audio, video, and data connections between users. To create those connections, the browser collects ICE candidates, which can include public IPs, local network IPs, IPv6 addresses, and mDNS candidates.

The issue is that WebRTC can use browser network interfaces separately from your normal web connection. That means your website traffic may go through a VPN or proxy, while WebRTC still reveals another IP path.

For proxy users, the fix is usually in the browser, anti-detect profile, or automation setup, not only in the proxy itself.

Setup

Does WebRTC leak?

Why

HTTP/HTTPS proxy

Usually yes

WebRTC can use UDP outside the HTTP proxy tunnel unless the browser blocks it

SOCKS5 proxy

Usually yes

Many browsers do not automatically route WebRTC candidates through SOCKS5

Residential, mobile, or ISP proxy

Usually yes

The proxy type does not control WebRTC by itself; browser WebRTC settings do

Anti-detect browser + proxy

Depends on settings

The profile must disable WebRTC or force WebRTC to return the proxy IP

Browser with WebRTC disabled + proxy

The browser cannot create WebRTC ICE candidates

Puppeteer / Playwright with WebRTC policy flag

No, if configured correctly

Chromium is forced to block non-proxied UDP or use the allowed network policy

A page creates a WebRTC connection

The website runs JavaScript that creates an RTCPeerConnection in your browser

The browser contacts a STUN server

The browser asks a STUN server which public IP address it can see over UDP

The browser collects ICE candidates

The browser gathers possible connection addresses, including public IPs, local IPs, IPv6 addresses, and mDNS candidates

JavaScript reads the candidates

The page can read candidate data from onicecandidate events or the session description, then compare it with your normal HTTP IP

Chrome and Edge

Install WebRTC Network Limiter and set the policy to use the default public interface only. For automation, launch Chromium with --force-webrtc-ip-handling-policy=disable_non_proxied_udp

Firefox

Open about:config, search for media.peerconnection.enabled, and set it to false if you want to fully disable WebRTC

Brave

Open Settings → Shields → Fingerprinting blocking and set WebRTC IP handling to a stricter privacy mode

Safari

Keep Safari updated and check privacy settings before sensitive sessions. Safari exposes fewer direct WebRTC controls than Chromium-based browsers, so use a WebRTC leak test after changing VPN, proxy, or network settings

Anti-detect browsers

Use the browser’s WebRTC protection setting to either disable WebRTC or force WebRTC to return the proxy IP

Puppeteer and Playwright

Launch Chromium with --force-webrtc-ip-handling-policy=disable_non_proxied_udp to prevent non-proxied UDP WebRTC traffic during browser automation

What is a WebRTC leak?

A WebRTC leak happens when your browser exposes your real public IP, local IP, IPv6 address, or mDNS candidate through WebRTC, even if your normal web traffic goes through a VPN or proxy.

How do I test for a WebRTC leak?

Run a WebRTC leak test and compare your HTTP IP with the IPs found in WebRTC candidates. If WebRTC shows a different public IP, local IP, or unexpected IPv6 address, your browser may be leaking.

Can WebRTC leak my real IP while using a proxy?

Yes. HTTP, HTTPS, and SOCKS5 proxies protect normal browser traffic, but WebRTC can use browser network interfaces separately. To prevent leaks, configure your browser, anti-detect profile, or automation environment to block non-proxied WebRTC traffic.

Do SOCKS5 proxies prevent WebRTC leaks?

Not by themselves. SOCKS5 proxies protect supported traffic, but WebRTC may still expose IP data unless your browser disables WebRTC, blocks non-proxied UDP, or forces WebRTC to return the proxy IP. NodeMaven proxies support SOCKS5, but WebRTC protection still needs to be handled in the browser.

Which NodeMaven proxies work best with WebRTC-protected browsers?

NodeMaven residential, mobile, and ISP proxies can all be used with WebRTC-protected browsers. Residential proxies are best when you need wide geo-targeting, rotation, and sticky sessions. Mobile proxies are useful for mobile-first platforms. ISP proxies are best when you need static IP identity, unlimited traffic, and long-running sessions.

Do anti-detect browsers prevent WebRTC leaks?

Many anti-detect browsers include WebRTC controls, but settings vary by profile. For proxy workflows, configure WebRTC to return the proxy IP or disable WebRTC, then run a leak test before using the profile. NodeMaven proxies work with common anti-detect browser workflows when the browser profile is configured correctly.

How do I fix a WebRTC leak in Chrome or Edge?

Use a WebRTC privacy extension such as WebRTC Network Limiter, set WebRTC to use the default public interface only, or launch Chromium with --force-webrtc-ip-handling-policy=disable_non_proxied_udp for automation workflows.

How do I disable WebRTC in Firefox?

Open about:config, search for media.peerconnection.enabled, and set it to false. This disables WebRTC peer connections and prevents the browser from creating ICE candidates.

What is the difference between a WebRTC leak and a DNS leak?

A WebRTC leak exposes IP information through browser peer-connection APIs. A DNS leak happens when domain lookups bypass your VPN or proxy and go to an unintended DNS resolver, often your ISP.