Your own resolver, before any connection was attempted.

ENOTFOUND — DNS lookup failed

The hostname did not resolve. Nothing was sent anywhere. Through a proxy this often means the DNS lookup happened LOCALLY when it should have gone through the proxy — which is also how a geo-targeted request quietly leaks your real location.

A proxy fixes part of this. Resolving through the proxy fixes both the failure and the leak, but only if the client is told to — that is the h in socks5h. Rotating IPs changes nothing here.

Get residential IPs →Web Unblocker

Why it happens

A typo in the hostname, or a domain that no longer exists.

SOCKS5 used instead of SOCKS5H, so the client resolved locally rather than through the proxy.

A local DNS server that cannot see the name, e.g. an internal host reached from outside.

A proxy env var set to a hostname the machine cannot resolve.

How to fix it

  1. Resolve the name manually — dig or nslookup answers this in a second.
  2. For SOCKS, use socks5h:// so the proxy performs the lookup. With socks5:// your resolver sees every domain you visit and the geo you paid for is undone before the connection starts.
  3. Check whether the failing name is the target or the proxy; the error looks identical either way.

FAQ

What does ENOTFOUND mean?›
The hostname did not resolve. Nothing was sent anywhere. Through a proxy this often means the DNS lookup happened LOCALLY when it should have gone through the proxy — which is also how a geo-targeted request quietly leaks your real location. Your own resolver, before any connection was attempted.
Why am I getting ENOTFOUND?›
A typo in the hostname, or a domain that no longer exists. SOCKS5 used instead of SOCKS5H, so the client resolved locally rather than through the proxy. A local DNS server that cannot see the name, e.g. an internal host reached from outside. A proxy env var set to a hostname the machine cannot resolve.
How do I fix ENOTFOUND?›
Resolve the name manually — dig or nslookup answers this in a second. For SOCKS, use socks5h:// so the proxy performs the lookup. With socks5:// your resolver sees every domain you visit and the geo you paid for is undone before the connection starts. Check whether the failing name is the target or the proxy; the error looks identical either way.
Will a proxy fix ENOTFOUND?›
Resolving through the proxy fixes both the failure and the leak, but only if the client is told to — that is the h in socks5h. Rotating IPs changes nothing here.

Other errors

ERR_EMPTY_RESPONSEERR_TUNNEL_CONNECTION_FAILEDERR_PROXY_CONNECTION_FAILEDECONNRESETETIMEDOUT407403429401502503504

Stop getting ENOTFOUND

Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.

Get residential IPs →