Skip to content
ScanMyPrivacy
Menu

Privacy and leak tests

Full Privacy ScanDNS Leak TestWebRTC Leak TestBrowser Fingerprint TestAm I Using a VPN?HTTP Headers ViewerUser Agent CheckerOpen Port Checker

Online safety assistant

Website Safety CheckerSuspicious Link CheckerScam and Phishing Message CheckerBrowser Security GuideMobile App Safety CheckPersonal Security Checkup

IP and network lookups

IP LookupMy IP LocationWhat Is My Public IP?What Is My IPv6 Address?Reverse DNS LookupDNS Lookup
Online safety Guides API About

Free WebRTC leak test

WebRTC Leak Test

Check whether your browser reveals your real IP address through WebRTC, even when a VPN is on.

Your WebRTC test

Runs automatically. Your browser asks a public STUN server what address it sees, and we compare the answer with the address websites see.

What we test, what we do not, and what we store

Full method →

We test

  • The addresses your browser reveals through WebRTC
  • Whether any public address differs from the one websites see for your connection

We do not test

  • Other kinds of leak: this tests WebRTC only
  • Leaks from apps outside the browser

What we store

  • Nothing: the comparison happens in your browser
  • Anonymous usage counts only: which tool was completed and a coarse result category, never what you typed, your IP address or your results. Nothing is sent if your browser signals Global Privacy Control or Do Not Track.

Third parties that see data: A STUN server (Google's by default) is contacted by your browser and sees the address your browser connects from. ipify and our own server provide the address websites see.

What is WebRTC?

WebRTC (Web Real-Time Communication) is the browser technology behind video calls, screen sharing and peer-to-peer file transfer. To connect two people directly, it needs to know each side's network addresses, so a web page is allowed to ask the browser to gather them. That request does not need your permission, and it bypasses the normal web path that a VPN or proxy controls.

Why WebRTC can leak your IP

A VPN changes the address that websites see on ordinary connections. WebRTC uses a different mechanism. It asks a STUN server, "what address are you contacting me from?", and it also lists the addresses on your device's network interfaces. If a script reads those results, it can learn:

  • your real public IP address if the STUN request escapes the VPN tunnel;
  • your public IPv6 address if the VPN does not cover IPv6;
  • your local network address (like 192.168.1.20), which helps fingerprint you.

How this test works

This page creates a WebRTC connection locally, asks a STUN server for your reflexive address and collects every candidate address the browser offers. It then compares each public address with the IPv4 and IPv6 addresses our server sees. A public address that differs is reported as a leak. Everything is computed in your browser. We receive nothing from the test.

The default STUN server is operated by Google, so Google briefly sees the address your browser contacts it from. That is the same address it would see if you visited any Google site. Self-hosters can change it with the STUN_SERVERS setting.

Reading the result

ResultMeaning
No WebRTC leak detectedWebRTC revealed nothing beyond the address websites already see.
Leaking an IP addressThe browser revealed a different public address. With a VPN on, it is most likely your real one.
Local address exposedA private address like 192.168.x.x was shared. Harmless to reach, but a fingerprinting aid.
No public address revealedThe STUN request was blocked or WebRTC is restricted. Good for privacy, but we could not fully verify.

Browser behaviour in practice

Modern browsers have reduced the problem. Chrome, Edge, Safari and Firefox hide local addresses behind random .local names unless you grant camera or microphone access. Brave and Firefox can also restrict which interfaces WebRTC uses. Public addresses are still exposed through STUN unless WebRTC is limited or disabled. Our guide to stopping WebRTC leaks has settings for each browser.

Last reviewed 2026-10-26. Found a mistake? Report a correction (how we handle them).

Fix it and learn more

How to Stop WebRTC LeaksStep-by-step settings to stop WebRTC leaking your real IP address in Firefox, Chrome, Edge, Brave and Safari, and how to confirm the leak is closed.VPN connected but your real IP is still visible: causes and fixesTest shows your real IP while the VPN says connected? Check IPv6, WebRTC, DNS, split tunnelling and a dropped tunnel in order, and how to confirm each.

Also check your…

DNS Leak TestSee which DNS servers answer your lookups, and whether your VPN leaks them.Am I Using a VPN?Check whether sites see you as a VPN, proxy or data-centre connection.Full Privacy ScanRun every check at once and get a 0–100 privacy score with fixes.HTTP Headers ViewerThe exact request headers every website receives from you.

Frequently asked questions

Is a WebRTC leak dangerous?

It exposes the address your VPN was meant to hide, so the website can see your real city and ISP. It does not give anyone access to your device.

How do I stop WebRTC leaks?

Restrict WebRTC in your browser (Firefox: set media.peerconnection.enabled to false; Brave: set the WebRTC IP handling policy; Chrome and Edge: use an official WebRTC limiting extension). Use a VPN client that blocks WebRTC leaks. See the full guide.

Will disabling WebRTC break anything?

Video-conferencing sites, some voice chat and some peer-to-peer tools will stop working or fall back to less direct connections. Many people only enable the restriction in a browser profile they use for private browsing.

Why does the test say "could not compare"?

If the browser reveals an IPv6 address but we could not detect an IPv6 address for your connection, we cannot tell whether it matches, so we mark it unverified rather than call it a leak.