Inspect your active connection for proxy headers, residential vs datacenter IP classification, Tor routing, and unauthorized WebRTC public IP exposure.
Advertisement
Live Connection Privacy Audit
Real-time browser socket & STUN inspection
Public IP Address
Detecting...
Proxy / VPN Likelihood
Residential (Clean)
WebRTC Leak Exposure
No Leaks Detected
WebRTC Discovered IP
Scanning STUN candidates...
Tor Exit Node Detection
Not a Tor Node
Carrier / Organization Type
Broadband / ISP
System vs IP Timezone Verification
Auditing browser vs carrier clock...
Advertisement
How to Check & Clear Proxy Settings in Your Operating System
Malicious software or ad injectors often install unauthorized local proxies (127.0.0.1:8080) to intercept banking and browsing traffic. Below are authoritative methods to verify your system proxy state:
Windows 11 / Windows 10 (Command Prompt & PowerShell)
Open Windows Terminal or Command Prompt as Administrator and run:
netsh winhttp show proxy
If direct access is reported (Direct access (no proxy server)), your system is clean. If an unauthorized proxy appears, purge it immediately:
netsh winhttp reset proxy
macOS Sequoia 15.x / Sonoma (Terminal)
On Apple Mac systems, inspect your primary Wi-Fi or Ethernet interface using the official networksetup tool:
networksetup -getwebproxy "Wi-Fi"
To inspect secure HTTPS proxies:
networksetup -getsecurewebproxy "Wi-Fi"
Apple iCloud Private Relay
iCloud Private Relay (available on macOS and iOS with iCloud+) uses a dual-hop cryptographic proxy design. Your initial request is encrypted so your ISP cannot see the website destination, while Apple's egress proxy (partnered with Cloudflare and Fastly) masks your public IP address. Our detector recognizes iCloud Private Relay egress nodes as secure privacy proxies.
In modern cybersecurity and privacy engineering, anonymity tools such as Virtual Private Networks (VPNs), SOCKS5 proxies, and Tor onion routing are designed to shield user origin IP addresses and encrypt transit data. However, implementation flaws in operating system routing tables and browser Web APIs frequently cause critical identity leaks.
1. Mechanics of WebRTC IP Leaks (CVE-2015-1360)
Web Real-Time Communication (WebRTC) is a standard browser specification enabling peer-to-peer audio, video, and data streaming without third-party plugins. To establish direct peer connections between nodes behind Network Address Translation (NAT) gateways, WebRTC executes Interactive Connectivity Establishment (ICE) using STUN (Session Traversal Utilities for NAT) servers.
During the STUN binding request, the browser generates candidate addresses that expose both your local LAN IP (e.g., 192.168.1.105) and your true public ISP routing address, completely bypassing active VPN tunnels. Because this occurs at the browser application layer, operating system routing rules often fail to redirect these UDP packets, causing severe deanonymization.
2. DNS Leak Vulnerabilities & Split-Tunneling Risks
A DNS leak occurs when DNS lookup requests continue to route to your local Internet Service Provider's recursive resolvers rather than passing through the encrypted VPN tunnel. Key causes include:
Windows Smart Multi-Homed Name Resolution: Windows 10 and 11 query all available network adapters concurrently and adopt whichever response returns fastest, routinely leaking domain queries to local physical adapters.
IPv6 DNS Leaks: When an internet connection supports dual-stack IPv4/IPv6 but the VPN tunnel routes only IPv4, native IPv6 DNS queries bypass the VPN entirely.
Misconfigured Split-Tunneling: Improper routing rules that exclude certain applications from the VPN adapter often expose systemic DNS queries to unencrypted local gateways.
3. HTTP Proxy Forwarding Headers & Fingerprinting
Transparent and anonymous HTTP proxies frequently append identifying headers to outbound requests:
X-Forwarded-For: Appends the originating client's IP address.
Via: Advertises proxy software version (e.g., Squid, Apache Traffic Server).
X-Real-IP: Exposes direct connection endpoints to reverse proxy balancers.
Only 'Elite' or High-Anonymity proxies strip all intermediary headers and match native TCP MTU (Maximum Transmission Unit) packet characteristics to prevent proxy detection engines from flagging traffic as automated or proxied.