WebRTC Leak Test
Quick browser-side ICE scan to see if WebRTC exposes addresses beyond your VPN or proxy. No server calls — unlimited runs.
Click Run to start.
ICE candidates
Compare results with the IP checker with VPN on and off. This is a heuristic scan, not legal advice on privacy.
WebRTC Leak Test FAQ
What is a WebRTC leak?
Some browsers can discover local or public IP addresses through WebRTC ICE candidates even when you use a VPN or proxy. Sites may read those candidates alongside your normal HTTP IP.
Does this test work with VPN or proxy enabled?
Yes. Run the test with protection off, then on. If new public IPs appear that do not match your VPN exit, or your real LAN IP shows up, review browser WebRTC settings and your VPN leak-protection options.
Why do I see a 192.168.x.x or 10.x address?
That is usually a private LAN candidate from your router or hotspot. It is not your public ISP IP, but it can still fingerprint your network setup when combined with other signals.
Is this test 100% accurate?
No tool is perfect. Browsers, extensions, and VPN clients behave differently. Treat this as a quick diagnostic, then confirm with the IP checker and your provider’s documentation.
Do you send my results to a server?
No. ICE gathering runs entirely in your browser. Chilly does not log candidates or store test history on this page.
How do I reduce WebRTC leaks?
Use a VPN with WebRTC leak protection, disable WebRTC in hardened browser profiles, or route sensitive work through proxies with consistent exit IPs. For automation, validate routes with the proxy checker.