ISPing.me

How to Test Whether Your Proxy Is Leaking Your Real IP?

💡 Key takeaways

How do you test whether your proxy is leaking your real IP? After turning on your proxy, check three things: the address WebRTC probing exposes, which servers handle your DNS lookups, and the state of your IPv6 egress. If any one of them shows an address from your local broadband connection in China, your proxy tunnel is leaking. A speed test that works doesn't mean the tunnel is airtight — run through the full self-check and seal every hole before logging into a core account.

Many people assume that once they click Connect in their proxy client, outside websites can only see the overseas server's exit address. In practice, an ordinary proxy tool often only handles regular web traffic — open ISPing.me and check it once on the homepage and you'll usually only see the surface-level exit — while several hidden channels deep in your local system quietly give you away.

The 3 Leak Points

The WebRTC interface built into your browser is the easiest hole for traffic to punch through. The technology was designed for real-time voice and video calls in the browser, and to keep latency as low as possible it bypasses your regular HTTP or SOCKS5 proxy settings and sends network probe packets straight to external STUN servers. A few lines of JavaScript on a web page are enough to read your local network segment — or even your real IP on your home broadband in China.

A DNS leak from direct domain resolution is just as common. When you type a target URL into your browser's address bar, the system first has to translate the domain name into a numeric address. If your proxy software doesn't force UDP port 53 queries through the tunnel, your computer asks your local broadband carrier's DNS servers directly. The moment the target site sees a lookup record from mainland China in its authoritative DNS logs, your cross-border proxy disguise falls apart. For how platforms spot proxy use, see How to Tell If an AI Platform Has Spotted Your Proxy.

The IPv6 channel in a dual-stack network is another hidden blind spot. Today, the optical modems from China's three major carriers ship with native dual-stack enabled by default, while a huge number of cheap proxy IPs only configure traditional IPv4 forwarding rules. When you visit a large overseas site that supports both stacks, your system prefers the local native dual-stack channel and connects straight to the target server, exposing your real physical location completely. For the underlying mechanics of all three leaks, see Check These Three Things Before Using Claude: WebRTC, DNS, and IPv6 Leaks.

Test Steps: Check All Three After Turning On Your Proxy

Knowing the theory isn't enough. Once you're connected, work through the checklist below in order — two minutes is all it takes to see whether your tunnel is airtight:

Leak channelWhere to check and what to doSafe resultSigns of a leak
Basic exit checkAfter turning on the node, open the ISPing.me homepage and run a queryShows the country where the overseas node is located, with purity <20 and sharing 1-10 ExcellentThe exit still shows your home broadband in China, or the proxy rules aren't taking effect
DNS resolution pathOpen the DNS leak test page and wait for the node scan to finishEvery DNS server listed is overseas and matches the exit countryThe list includes a resolver from China Telecom, China Unicom, or China Mobile
Browser peer-to-peer probingCheck the local candidate addresses the page captures and the dual-stack connection statusOnly the proxy exit address is returned, or probing shows as disabled, with no native dual-stack direct connectionThe candidate list shows a public segment from your local broadband, or a domestic dual-stack address

When you run the test, first switch your proxy client to the working mode you plan to use (for example, rule-based split routing or global forwarding) and turn off any unrelated browser proxy extensions so they don't interfere with each other. Then open the dedicated DNS leak test page and let the system automatically send resolution probes to several groups of authoritative overseas nodes. Wait about ten seconds for the results to load, then look carefully at the flags and organization names of the DNS servers listed — if even one record from a domestic carrier sneaks in, you've confirmed a serious DNS leak. For a detailed breakdown of the detection metrics, see What Is a DNS Leak? How to Detect It.

After the DNS check, move on to browser peer-to-peer probing and dual-stack connectivity. Look at the candidate address list in the test results: in a properly sealed tunnel, only the address of the overseas server you're connected to shows up. If the list suddenly shows a public address starting with your domestic broadband segment, or the dual-stack connectivity field directly displays the native address your local carrier assigned you, your real IP has already slipped out through your local network card.

What to Do If You're Leaking

For the browser peer-to-peer hole, the fix is straightforward. If you use Chrome or Edge, go to the extension store and install a well-established open-source plugin (such as WebRTC Network Limiter), open its options after installing, and check "Use only the default public interface (disable non-proxied UDP traffic)." If you use Firefox, type about:config in the address bar, search for media.peerconnection.enabled, and double-click it to change the value to false — that cuts off the WebRTC probing channel at the root.

Sealing direct DNS resolution takes both the client and the system working together. Open your proxy tool's core network settings and force on the "Remote DNS resolution" or "DNS hijacking" switch, and enable the virtual network card (TUN mode) to take over UDP traffic at the system level. As a second layer of protection, go into your computer's network adapter properties and manually set the IPv4 primary and secondary DNS addresses to public overseas resolvers (for example, 1.1.1.1 and 8.8.8.8) to eliminate any DNS leak risk for good.

The simplest fix for the dual-stack direct-connection hole is to disable the IPv6 protocol stack on your local computer. Open Windows "Network and Sharing Center -> Change adapter settings," right-click the Wi-Fi or Ethernet connection you're currently using and choose "Properties," then uncheck Internet Protocol Version 6 (TCP/IPv6) in the list and click OK. After that, all network requests are forced through the proxy-protected IPv4 channel — it won't affect normal access to domestic websites, and it completely stops dual-stack address leaks.

How to Confirm a Proxy Won't Leak Before You Buy

Beyond getting your local software configured, you should also make leak-proofing part of your acceptance standard when choosing a line. Many budget providers ship bare-bones gateway configurations for their regular proxy IPs: the server doesn't support remote DNS forwarding at all, and may even write your client's real source address into the X-Forwarded-For HTTP header and pass it to the target site. That's a transparent or anonymous proxy — no local setting will stop it from giving you away. For why regular proxy lines carry a higher risk weight, see Why Is a Proxy IP's Risk Score Higher Than a Residential IP's?.

When buying a line for high-risk business, prioritize a well-managed, highly anonymous native residential IP. A genuine dedicated residential IP gateway usually forwards traffic through a highly anonymous encrypted tunnel. Before ordering, ask the seller for a test port; once connected, first check that the exit's IP purity falls in the <20 Pure tier and that concurrent sharing stays in the 1-10 Excellent range. Then immediately run the full leak test to confirm the server has stripped all proxy-identifying headers and fully handles remote DNS resolution. Only pay in bulk once you've confirmed the whole tunnel is airtight and the exit score holds steady in the low-risk range over time. For troubleshooting a high-scoring exit, see What to Do About a High IP Risk Score? How to Lower It. For the full pre-purchase verification process and sharing-count tiers, see How to Verify a Proxy Before You Buy It and What Is the IP Sharing Count, and Why Does It Matter?.

FAQ

Why does the test still report a DNS leak even though I turned on global mode in my proxy software?
Because many proxy clients' global mode only handles TCP web traffic and doesn't hijack the system's UDP port 53 DNS queries. You need to turn on "Remote DNS resolution" in the proxy software's settings, or enable "TUN virtual network card mode," to lock DNS lookups inside the encrypted tunnel.

Will turning off IPv6 on my computer affect normal access to domestic websites and video streaming?
Not at all. The vast majority of domestic websites, video platforms, and office software in China fully support the IPv4 stack. Turning off the local dual-stack channel only stops some dual-stack-capable overseas sites from bypassing your proxy and connecting straight to your local broadband — your everyday domestic internet speed won't change at all.

How do I prevent WebRTC and real-location leaks when using a proxy on my phone?
Three steps on mobile: turn off the "Precise location" permission for apps in your phone's system settings; turn on airplane mode, then connect to Wi-Fi, so cellular tower signals can't expose your home region; and in your proxy software's settings, turn on "Remote DNS forwarding" and disable dual-stack routing.

What are transparent, anonymous, and elite proxies? Which one won't leak my real IP?
A transparent proxy exposes your real address to websites. An anonymous proxy hides your real address but tells the website in its request headers that you're using a proxy. Only an elite (high-anonymity) proxy strips proxy-identifying headers so the target server treats you as an ordinary direct user — look for the elite type when buying a proxy.

Notes

Check whether your proxy leaks your IP

Check your network environment on ISPing.me — confirm the purity, sharing count, and risk signals, and only use it once it passes.

Check now

Related reading:What Is a DNS Leak? How to Detect ItCheck These Three Things Before Using Claude: WebRTC, DNS, and IPv6 LeaksHow to Choose a Proxy IP: A Guide to Avoiding Pitfalls and Picking RightWhat Is IP Purity? How to Read the Risk ScoreWhy Is a Proxy IP's Risk Score Higher Than a Residential IP's?What to Do When Detection Results Don't Match Real UsageWhat to Do About a High IP Risk Score? How to Lower It

IP Knowledge Base