WebRTC Leak Test
Check whether your browser exposes your real IP address, or a different one, through WebRTC while a VPN is connected. No sign-up, results in seconds.
- Runs in your browser
- Your IP is not stored
- No sign-up needed
- Free to use
Run the free test
Run it once with your VPN off (baseline) and once with it on. Comparing the two gives the clearest answer.
Is your VPN connected right now?
Optional: run once with VPN offAfter the testAfter the testThe test uses only RapidPing’s own STUN server and servers; no third-party STUN or IP lookup service is involved. Our server sees your public IP like any website you visit, uses it only to compare addresses during this request, and does not store or log it. The baseline stays in this browser tab only. Last updated: November 2026.
What the results mean
Three possible results and what to do about each.
No leak observed
WebRTC shows the same IP as your browser, and your real IP did not appear.
Leak confirmed or possible
WebRTC shows your real IP, or an IP that differs from the one websites see. Close the leak below and test again.
Inconclusive result
WebRTC is blocked, the STUN servers were unreachable, or the addresses could not be compared. That does not mean you are safe; try again or use another browser.
What do the addresses in the details mean?
- Baseline: your real IP while the VPN is off. If it shows up through WebRTC while the VPN is on, the leak is confirmed.
- Public IP via WebRTC (srflx): the address a STUN server sees. This is what the verdict is based on.
- Address on the device (host): addresses like
192.168.x.x, carrier100.64.x.xor a global IPv6 on your network card. They are informational and not used for the verdict. - mDNS name (.local): a random name browsers show instead of your local IP, which means your local address stayed hidden.
- The IP websites see comes from your browser’s normal requests, and WebRTC can reveal others through STUN. The two are compared separately for IPv4 and IPv6.
Why test for WebRTC leaks?
When a VPN is connected, you expect websites to see only the VPN server’s IP. WebRTC can break that and expose your real IP, although many current browsers and VPNs already block it, which is why the test checks what is actually exposed.
Linked to your real connection
Websites may be able to tie your visits to your actual internet connection, which weakens your privacy.
Your approximate location shows
Your real IP may reveal your country, approximate region and internet provider.
The gap between two connections
If both IPs (the VPN’s exit and your real one) are visible, a site can tell two different connections are in use.
How to prevent WebRTC leaks
Pick the option that fits how you use your browser.
VPN on the whole device
Instead of changing browser settings, turn the VPN on for your whole phone or computer: open the WireGuard app, import your RapidPing config and connect. From then on, every app, including your browser, uses the VPN. If you edited the config yourself, AllowedIPs should include 0.0.0.0/0 and ::/0. A plain proxy app, such as V2Ray without TUN mode, may not carry WebRTC.
Browser setting
Firefox has a simple setting to turn WebRTC off. In Chrome and Edge, use a full tunnel or an extension. Step-by-step guide ↓
Test again
After every change, reload this page and run the test with your VPN on.
Browser settings to prevent WebRTC leaks
Which fits you? If you use Firefox, the browser setting is the simplest way. In Chrome, Edge and others, a VPN on the whole device is the more reliable choice.
- Type
about:configin the address bar and press Enter. - Confirm the warning with “Accept the Risk and Continue”.
- Search for
media.peerconnection.enabled. - Set its value to
false.Click the toggle icon next to it. - Reload this page and test again.
Chrome and Microsoft Edge have no simple built-in setting to turn WebRTC off completely. You have two options:
- VPN on the whole device (recommended)Open the WireGuard app, import your config and connect. From then on, every app, including Chrome and Edge, uses the VPN.
- A trusted extension (if needed)Use a trusted WebRTC-management extension. Before installing, check the publisher, user reviews and requested permissions.
- Reload and test again
We don’t know of a simple switch for Safari and other browsers. A VPN on the whole device is the more reliable choice; after connecting, run the test again.
No extension or browser setting guarantees a leak is closed on its own. To be sure, compare the test result with your VPN off and on.
How does the test work?
Your browser asks a STUN server
The page starts a short-lived WebRTC connection, which makes your browser look up the addresses it could be reached on.
We collect every address it finds
That includes your public IP, local network addresses and, with a leaky setup, your real IP outside the VPN.
We compare them with your visible IP
If WebRTC reports a public IP that differs from the one websites see, it points to a possible leak.
Try your connection with RapidPing
Repeat the test over a real VPN connection and compare it with your earlier result.
- 300 MB
- 3 hours
- No payment
- Sign up
- Verify email
- Test in your dashboard
- Supports V2Ray and WireGuard
- Pay with crypto
- No auto-renewal
- No VPN activity logs
Questions
What is a WebRTC leak?
WebRTC lets browsers make direct connections for calls and video. To do that it can reveal your IP addresses to websites, sometimes including your real IP while a VPN is connected.
Does WebRTC always show my real IP?
No. Many modern browsers and VPNs block it, but in some setups a public IP can still be exposed through a STUN server. This test shows what your browser exposes right now.
How do I fix a WebRTC leak?
Use a VPN on the whole device or limit WebRTC in your browser, then test again. The details are in “How to prevent WebRTC leaks” above.
Will disabling WebRTC break anything?
It can break browser-based video calls, voice chat and screen sharing. Websites and downloads keep working normally.