← All posts

How to check a proxy for IP leaks (all six kinds)

You set up a proxy, open a site that shows your IP, and it shows the proxy's address. Done? Not quite. A browser has several ways to reveal the network it really sits on, and an "IP check" page tests only one of them.

This guide explains each kind of leak in plain words, how to test for it yourself, and how to fix it.

1. The plain IP

What it is: the address a website sees when your browser connects.

How to test: open two or three different "what is my IP" services through the profile. All of them should show the proxy's exit IP — and the same one.

If it shows your own IP: the browser isn't using the proxy at all. Check that the profile has the proxy set, and that the proxy accepted the connection (a profile that can't reach its proxy should refuse to start, not fall back to your connection).

2. IPv6

What it is: many connections now have an IPv6 address next to IPv4. Some proxies only carry IPv4; if the browser can still reach IPv6 sites directly, those sites see your real IPv6 address.

How to test: use an IP service that reports IPv6 as well, through the profile.

Fix: a proxy that handles IPv6, or a setup where the browser only connects through the proxy (no direct route around it).

3. WebRTC

What it is: WebRTC lets web pages make direct connections for calls and file transfers. To set them up, a page can ask the browser for the computer's addresses — including your real public IP and local network addresses — even through a proxy.

How to test: a WebRTC leak test page lists every address the browser reveals. None of them should be yours.

Fix: set WebRTC to send traffic through the proxy only (or disable it). In OwlXBrowser that's the default for every profile; "Real" WebRTC is only meant for profiles without a proxy.

4. DNS

What it is: before connecting to example.com, the browser asks a DNS server for its address. If that question goes to your internet provider's DNS server instead of through the proxy, the site doesn't see your IP — but anyone watching DNS (your provider, the DNS service, and through some tests, the site) learns which sites you visit and where you really are.

How to test: a DNS leak test page loads a few unique names and reports which DNS servers looked them up. They should belong to the proxy's network, not your provider's.

Fix: SOCKS5 proxies can resolve names on the proxy side. With HTTP proxies, the proxy usually resolves the name for HTTPS connections; check with the test.

5. Forwarding headers

What it is: some proxies add headers such as X-Forwarded-For or Via to every request — and some put your real IP in them. These "transparent" proxies tell every site exactly who you are.

How to test: a header-echo page shows the headers it received. Look for forwarding headers and any IP in them.

Fix: use another proxy. A proxy that forwards your IP can't be configured into a private one from your side.

6. Connections around the proxy

What it is: a browser can make connections that don't go through the proxy at all — for example UDP traffic, or a misconfigured extension. Websites may not see these directly, but they reveal your network to whoever receives them.

How to test: this one needs a tool that watches the browser process's connections while pages load.

Fix: a browser setup that routes everything through the proxy and blocks direct UDP.

Test them all at once

Running six tests by hand for every profile is tedious, so the desktop app does it for you. In a profile's menu, Leak check opens the profile, loads test pages from inside it for about 40 seconds, and compares what each test sees with your computer's own public address:

  • sites (several IP services), IPv6, WebRTC, DNS, forwarding headers, and direct connections around the proxy (on Windows).

"No leaks: sites see only the proxy" means every test passed. If something leaks, the result says what and where, and Copy result gives you a version with your own IP hidden that you can share with support. Your own address is looked up only to compare, and is sent nowhere.

Good habits

  • Check a profile when you set it up and again after changing its proxy.
  • Keep each profile's time zone and language matched to the proxy; a perfect IP with a mismatched clock is its own kind of leak.
  • Prefer stable, reputable proxy providers. Free proxies are a common source of transparent proxies and logged traffic.

A proxy hides you only as well as its weakest path. Testing all six closes the gap between "the IP check looks fine" and "the site really sees only the proxy".