Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

DNS leak test through a proxy: who looks up the names you visit

Which resolver looked up the name in a DNS leak test through a proxy: with an HTTP proxy and with socks5h the lookup happened on the proxy side, in the United States or the Netherlands; with plain socks5 curl resolved the name on our own line and the test reported a resolver in Italy; the card sums up the rule: let the proxy resolve.
Which resolver looked up the name in a DNS leak test through a proxy: with an HTTP proxy and with socks5h the lookup happened on the proxy side, in the United States or the Netherlands; with plain socks5 curl resolved the name on our own line and the test reported a resolver in Italy; the card sums up the rule: let the proxy resolve.

A DNS leak test shows which DNS resolver looked up the sites you visit. Through a proxy, the lookup should happen on the proxy side. In our tests it did with HTTP proxies and with socks5h. With plain socks5, curl looked up names on our own connection, and the test reported our resolver in Italy: a leak.

We ran the checks on 20 November 2026 from an Italian broadband line, with curl 8.21.0 and with Chromium 149, through QuanticData Residential Basic, Residential Premium and Mobile. Resolver and exit IPs are masked.

What a DNS leak is, and why it matters with a proxy

Before a client can connect to a site, the site's name has to be turned into an IP by a DNS resolver. If your client asks your own resolver while the page itself comes through a proxy, two things happen: your internet provider's resolver logs every name you visit, and the site's DNS servers see a lookup from your country while the page request arrives from the proxy's. That mismatch is what leak tests look for.

Who resolves depends on the protocol, not on the proxy brand:

Proxy settingWho resolves the nameLeaks DNS?
HTTP proxy (http://, CONNECT for HTTPS)The proxy: the client sends it the host nameNo
SOCKS5 with remote resolution (socks5h://)The proxy: the client sends it the host nameNo
SOCKS5 with local resolution (socks5:// in curl)Your own resolver: the client sends the proxy an IPYes

Run a DNS leak test from the command line

edns.ip-api.com answers with the resolver that looked up a one-time name it made up for your request, so no cache can hide the result. One command per setup:

curl -L http://edns.ip-api.com/json
curl -L -x http://USER:PASS@residentialpremium.quanticdata.io:8080 http://edns.ip-api.com/json
curl -L -x http://USER:PASS@mobile.quanticdata.io:8080 http://edns.ip-api.com/json
curl -L -x socks5h://USER:PASS@mobile.quanticdata.io:1080 http://edns.ip-api.com/json
curl -L -x socks5://USER:PASS@mobile.quanticdata.io:1080 http://edns.ip-api.com/json
SetupResolver the test sawResult
No proxyItaly, CloudflareOur own resolver (the baseline)
Residential Premium, HTTPNetherlands, GoogleResolved on the proxy side
Mobile, HTTPUnited States, CloudflareResolved on the proxy side
Mobile, socks5hUnited States, CloudflareResolved on the proxy side
Mobile, socks5Italy, CloudflareLeak: resolved on our line

The proxy was the same mobile gateway in the last two rows. The only change was one letter in the scheme, and it moved the lookup from the United States back to Italy. In curl, socks5h:// (or --socks5-hostname) means "let the proxy resolve"; socks5:// means "resolve here, send the proxy an IP". More curl proxy options are in how to use a proxy with curl, and more on the protocol on our page for SOCKS5 proxies.

curl -L -x socks5h://USER:PASS@mobile.quanticdata.io:1080 http://edns.ip-api.com/json
{
    "dns": {
        "geo": "United States - Cloudflare, Inc.",
        "ip": "x.x.x.x"
    }
}

curl -L -x socks5://USER:PASS@mobile.quanticdata.io:1080 http://edns.ip-api.com/json
{
    "dns": {
        "geo": "Italy - Cloudflare, Inc.",
        "ip": "x.x.x.x"
    }
}

A DNS leak test in the browser

We opened browserleaks.com/dns, which looks up 50 random names and lists the resolvers that asked for them, in Chromium 149 set to use each of our three networks over HTTP:

NetworkExit the page sawResolvers listedIn Italy?
Residential Premium, GermanyVodafone Kabel Deutschland, GermanyGoogle (Groningen, Netherlands), Vodafone Kabel DeutschlandNo
Mobile, USVerizon Business, USGoogle (Council Bluffs), Cloudflare (Chicago), Verizon Business (Boston)No
Residential Basic, USRCN, AshburnGoogle (Morganton)No

Every resolver sat in the proxy's country or next to it, and none in Italy. A browser set to an HTTP proxy hands the host names to the proxy, so the lookups happen there.

How to read a DNS leak test result

  • Start from a baseline. Run the test once without the proxy and note the resolver: for us, Cloudflare in Italy. A leak is that same resolver showing up while the proxy is on.
  • A resolver in a neighbouring country is normal. Public resolvers run in many data centres, and the one that answers is not always in the exit's country: our German Residential Premium exits were served from the Netherlands.
  • Several resolvers are normal too. browserleaks.com looks up 25 IPv4-only and 25 IPv6-only names, and big resolver networks spread them over several servers: the mobile run listed three providers in three US cities.
  • The resolver's company does not matter, its location does. Cloudflare appeared both in the leak and in the clean runs; what changed was Italy versus the United States.

How to fix a DNS leak with a proxy

  • Use socks5h://, not socks5://, wherever the tool offers both: curl, and libraries that follow curl's naming.
  • Pick the form that resolves at the proxy. Use the HTTP form of the proxy, or SOCKS5 with remote resolution.
  • Rerun the test after every change and compare with your baseline without proxy.
  • Check WebRTC too: it is the other usual leak in a browser, covered in our WebRTC leak test.

A VPN routes all of a device's lookups and needs its own DNS setting; the differences are in residential proxy vs VPN.

Residential or mobile, with lookups on the proxy side

When the lookup happens at the proxy, the site's DNS and its web server see the same side of the world. Residential Basic and Premium give home IPs in the country you pick; Mobile gives carrier IPs. See residential proxies and mobile proxies, or start with the Residential Basic free trial. To see how IP databases place an exit, use our proxy location checker; for the rest of what a site can learn, read how to hide your IP address.

Sources & further reading

FAQ

Quick answers on dns leak test.

Something else? Ask us

What is a DNS leak?

When the names you visit are looked up by your own resolver while your traffic goes through a proxy or VPN. Your provider can log the names, and sites can see a lookup from your country next to a request from the proxy's.

Do proxies leak DNS?

It depends on the setting. In our tests, HTTP proxies and socks5h resolved names on the proxy side. Plain socks5 in curl resolved them on our own line, and the test reported our resolver in Italy.

What is the difference between socks5 and socks5h?

With socks5h:// the proxy resolves the host name; with socks5:// the client resolves it and sends the proxy an IP. Through the same mobile gateway, socks5h gave a resolver in the United States and socks5 one in Italy.

How do I run a DNS leak test?

Compare the resolver a test reports without the proxy and with it. From the command line, curl -L -x PROXY http://edns.ip-api.com/json; in a browser, a DNS leak test page through the proxy. A resolver in your own country through the proxy is a leak.

Does an HTTP proxy hide my DNS lookups?

For the requests it carries, yes: the client sends the host name to the proxy, which resolves it. Through our Residential Premium and Mobile HTTP gateways, the resolvers were in the Netherlands and the United States, not Italy.

Proxies that resolve on their side

Residential and mobile proxies in the country you pick, with name lookups done on the proxy side.

Related reading