Skip to main content

Free WebRTC IP Leak Test

Check whether WebRTC is leaking your local network address or your real public IP around your VPN. Runs a genuine peer connection in your browser using public STUN servers β€” nothing is uploaded.

How this works. Your browser opens a genuine WebRTC peer connection and asks public STUN servers (Google, Cloudflare) to help discover your reachable addresses. The IPs it offers at that step are exactly what any website can collect β€” including around a VPN if WebRTC isn't blocked.

Nothing about your browser is sent to LibraTool. The STUN servers see only the standard ICE handshake.

The optional compare button is the one exception: it makes a single request to Cloudflare (and api64.ipify.org if that fails) so you can see which address websites see.

How It Works

Opens a real WebRTC peer connection in your browser and lists every IP address it discovers β€” exactly the addresses any website using WebRTC could see, including over a VPN if WebRTC is not blocked.

  1. 1
    Your browser starts an ICE negotiation
    A peer connection is created locally and asked to gather candidate addresses, including by querying public STUN servers (Google, Cloudflare) for your reachable public IP.
  2. 2
    IP addresses are categorized
    Private RFC1918 ranges (192.168/10/172.16) and IPv6 link-local are flagged as local; everything else is public. Modern browsers anonymize LAN IPs as mDNS .local β€” raw 192.168 addresses mean that protection is off.
  3. 3
    Compare with your VPN exit
    If a VPN should hide your IP, the public IP shown here must match the VPN exit, not your home ISP. If it shows your home IP, WebRTC is leaking around the VPN.

The peer connection only contacts public STUN servers. LibraTool sees nothing β€” your IPs are displayed in your browser only.

Related Tools

Frequently Asked Questions