WebRTC Leak Test
Check whether WebRTC exposes your real IP address — even behind a VPN.
WebRTC is the browser technology behind video calls and voice chat in the browser. To connect two browsers directly it uses a process called ICE, which collects every network address that might reach your device — local addresses, and your public address as seen by a STUN server. Any website can trigger this collection with a few lines of JavaScript, no permission prompt required.
Compare the public address above with What Is My IP — if they differ while you are on a VPN, your real IP is leaking.
How to use
- Press "Run the test" (it also runs once automatically when the page loads) and wait a few seconds while your browser gathers ICE candidates.
- Read the table: every address WebRTC can see is listed with its candidate type and what it means.
- If you use a VPN, compare the public address shown here with What Is My IP. Different addresses mean your real IP is leaking around the VPN.
About this tool
That is the leak: if you browse over a VPN but WebRTC reports the public address of your real connection, a site can see both addresses and work out who you are. Modern browsers blunt the local part of the problem by replacing your local IP with a random mDNS name ending in .local — if you see one of those in your results, that protection is working and it is not a leak.
This test runs the standard ICE gathering process locally in your browser and shows you exactly what it finds. The addresses are displayed to you only; they are not sent to us or stored. Your browser does contact public STUN servers (operated by Google and Cloudflare) as part of the test — that is how WebRTC learns your public address.
Frequently asked questions
What is a WebRTC leak, in one sentence?
A website learning your real public IP address through WebRTC even though your normal traffic goes through a VPN — the addresses differ, and the difference identifies your actual connection.
I see an address ending in .local. Is that a leak?
No — it is the opposite. Browsers substitute a random .local mDNS name for your real local IP precisely so sites cannot learn it. Seeing .local means the protection is on.
How do I stop a real leak?
Use a VPN that explicitly handles WebRTC, disable WebRTC in your browser settings or with a reputable extension, or use a browser with WebRTC restrictions built in. Retest here afterwards to confirm.
Do you store the addresses this test finds?
No. They are collected by your browser, rendered into this page, and gone when you close the tab.
More free tools
UUID Generator
Generate random v4 UUIDs in bulk.
Base64 Encode / Decode
Encode text to Base64 or decode it back.
Color Converter (HEX ↔ RGB)
Convert HEX to RGB and back, with live preview.
JSON Formatter & Validator
Format, minify and validate JSON in one click.
What Is My IP
See your public IP address instantly. No sign-up, nothing stored.
URL Encoder / Decoder
Encode or decode URLs and query strings.