Acerca de Fugas del navegador
Inspeccionar las rutas IP, WebRTC y DNS visibles para el navegador
A browser leak check describes what this browser and network exposed during one run. It cannot read the operating system proxy setting directly, and a result is not a complete anonymity, VPN, or security audit.
Cómo usar esta herramienta de desarrollo
- Run the direct browser checks to see the IPv4 and IPv6 paths visible to the page.
- Review local and server-reflexive WebRTC candidates and compare them with the VPN or proxy behavior you expect.
- Wait for the one-time DNS probes to finish and review the resolver signals returned by the controlled probe domains.
- Repeat after changing browser, VPN, proxy, or network settings, and confirm important findings with the provider's own documentation.
Privacidad y tratamiento de datos
This tool runs in the browser. It gathers WebRTC candidates locally, connects to configured IP detection endpoints, and makes one-time DNS probe requests to controlled domains. It does not send browser-leak results to this site's server, and it cannot read system proxy settings or collect proxy credentials.
Herramientas de desarrollo relacionadas
Preguntas frecuentes
Can a website read my system proxy setting?
No. A normal web page cannot directly inspect the operating system's proxy configuration. It can only compare the network paths and signals exposed by the browser.
What does a WebRTC candidate reveal?
A candidate can show a local, server-reflexive, relay, or mDNS-hidden path exposed for WebRTC. Its significance depends on browser policy, VPN design, and the application using WebRTC.
What does a DNS leak result prove?
It indicates which resolver path handled the probe requests observed by the controlled domains. It is a useful signal, not a complete inventory of every DNS request from the device.