Free tool · Nothing stored

WebRTC leak test

A VPN hides your address from websites, but WebRTC can reveal it. This test compares the addresses WebRTC finds with the one websites see.

WebRTC addresses

Turn your VPN on first. The test takes up to 6 seconds.

What each result means.

You seeWhat it means
A public address matching what websites seeNo leak. With a VPN on, that is the VPN’s address.
A public address websites don’t seeWith a VPN on, WebRTC is going around it.
A name ending in .localThe browser is hiding your local address.
A private address such as 192.168.x.xYour local address. It isn’t visible from the internet.
Nothing public at allThe browser, VPN or network stopped WebRTC reaching the STUN server.

Also check the DNS leak test and what websites see as your IP address.

More checks for your connection.

Questions

What is a WebRTC leak?

WebRTC lets browsers connect directly for calls. To do that, a page can ask the browser for its network addresses. If WebRTC finds a public address outside your VPN, the page can learn your real address.

How does this test work?

It starts a WebRTC connection attempt with Cloudflare’s public STUN server, which reports the public address it sees. The page compares that with the address websites see.

The test shows an address that isn’t my VPN’s. What now?

With a VPN on, that address is probably your real one. Update the VPN app, look for leak protection in its settings, and run the test again. With no VPN on, a different address is normal.

What are the .local names?

Browsers hide your local address behind a random name ending in .local, using mDNS. It means the page can’t read your address on your own network.

Is a local address a leak?

Not by itself. A local address such as 192.168.1.20 only works on your own network and doesn’t identify you to the wider internet.

Does this test store my address?

No. The comparison runs in your browser, and nothing you see here is saved.

How do I check a VPN on a Mac?

Run kilobat vpn leaks in Terminal. Kilobat checks for leaks from the whole Mac, not only this browser. For DNS, run the DNS leak test.

Sources

  1. RFC 8828: WebRTC IP Address Handling Requirements
  2. IETF draft: Using Multicast DNS to protect privacy when exposing ICE candidates
  3. RFC 8489: Session Traversal Utilities for NAT (STUN)
  4. MDN: RTCPeerConnection
  5. Cloudflare Realtime: TURN and STUN service addresses

Checked on 8 November 2026.

Check your VPN, DNS and network from the whole Mac.

Download for Mac ↓
brew install seifip/kilobat/kilobat