How do you know if your browser is leaking IPs via WebRTC?
If the WebRTC IP differs from the IP seen by websites, WebRTC is bypassing the proxy and leaking your real IP; if both IPs match or no public IP is detected, there is no leak.
- IP seen by websites: the address routed through your proxy or VPN, detected from the server.
- IP via WebRTC: the address reported by the browser when querying STUN servers.
- Both addresses match, or WebRTC returns no public IP: no leak.
- IP via WebRTC differs from the IP seen by websites: WebRTC is taking a separate route and exposing your real IP.
- Addresses ending in xxxx.local are internal IPs masked by your browser, no need to worry.
How do you block WebRTC leaks?
It depends on the browser: choose replacement or disabled WebRTC mode in antidetect browsers, disable WebRTC in Firefox, or use an extension to restrict WebRTC in Chrome or Edge.
- Antidetect browsers: choose the "replace" or "disable" WebRTC mode in your profile settings so the browser reports the proxy IP.
- Firefox: open about:config and set media.peerconnection.enabled to false.
- Chrome, Edge, Cốc Cốc: install an extension to restrict WebRTC, or configure your proxy at the system level instead of just in the browser.
- After making changes, reload this page to retest.
Dedicated proxies for each profile
Each dedicated IPv4 proxy from ONET provides a dedicated IP for a single customer, entered directly into antidetect profiles as ip:port:user:pass. Available in 9 countries with unlimited bandwidth.
Dedicated IPv4 proxies in 9 countries from 20.000 ₫/IP/month
View dedicated IPv4 proxy pricing