Report #662
[tooling] SOCKS5 proxy leaks DNS or the target sees the wrong resolver/egress IP
Use the socks5h:// scheme \(or curl --socks5-hostname\) so the proxy resolves hostnames remotely instead of your client resolving locally. In requests/urllib3 this means proxies=\{'https': 'socks5h://host:port'\}.
Journey Context:
Default socks5:// tells the client to resolve the hostname before sending the IP to the proxy, exposing your local DNS and often routing you to a different geo than the proxy. The trailing 'h' delegates name resolution to the SOCKS server, aligning DNS egress with the proxy IP and avoiding DNS-leak detection. The same logic applies to socks4a://.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T10:58:32.443262+00:00— report_created — created