Skip to content

How to Get a Free SOCKS5 Proxy (and Test It)

A SOCKS5 proxy can be free without being anonymous or trustworthy.

OUTPUT FORMATSHTMLJSONMarkdown

The two setups you control are a local Tor service and an SSH dynamic tunnel to a server you already own. Public SOCKS5 lists exist too, but their speed, uptime, and operator are unknown. This guide walks through both self-hosted routes, shows how to confirm the exit IP, and explains when a public proxy is a bad trade.

Pick the route that matches your trust level

Before touching a terminal, decide what the proxy is for.

  • Tor routes traffic through the Tor network. Good for low-volume, privacy-oriented requests where latency is tolerable. No account or server needed.
  • SSH dynamic tunnel borrows the public IP of a machine you already control. Good when you need a stable, known exit address and can keep a session open.
  • Public SOCKS5 list is the cheapest option on paper and the riskiest in practice. You cannot verify who runs the endpoint or what it logs.

If the task involves credentials, payments, or anything sensitive, skip the public list entirely. A SOCKS5 proxy does not encrypt application traffic on its own, so HTTPS still matters, and an unknown operator can still observe connection metadata.

Run Tor as a local SOCKS5 proxy

Tor exposes a local SOCKS proxy that supported applications can use to send traffic through the Tor network. Install and start Tor for your operating system using the official download page.

Default listening addresses:

  • Tor service: 127.0.0.1:9050
  • Tor Browser: 127.0.0.1:9150

Use the port that matches what you actually started. If you launch Tor Browser, point clients at 9150; if you run the standalone service, 9050 is the usual choice.

Verify the Tor proxy with curl

Send a request through the local proxy and print the public IP the destination sees. The protected command module code0001 contains the exact curl invocation for port 9050; run it in a terminal where Tor is already listening.

The output should be an IP address that differs from your normal one. The address can change between runs because Tor picks different exit nodes. The socks5h:// scheme matters: it tells curl to let the proxy resolve the destination hostname rather than resolving it locally, which avoids leaking DNS lookups outside the tunnel.

To compare, run the plain request in code0002 without a proxy. If both commands return the same IP, the proxy is not actually being used. The screenshot reference image0002 shows what a successful proxied result looks like in a terminal.

Create a SOCKS5 proxy over SSH

If you have SSH access to a remote server, you can open a local SOCKS5 proxy that forwards traffic through that host. The protected command module code0003 shows the dynamic-forward invocation on port 1080; replace the placeholder user and host with your own SSH username and server address.

Keep that terminal session open. In a second terminal, run the verification command in code0004 to confirm the exit IP. A successful result shows the public IP of the remote SSH server, not your local one.

This route is only as trustworthy as the server you control. It is not a way to hide from that server's operator, because you are the operator.

Port and scheme reference

A quick map of the values used above:

  • 127.0.0.1:9050 — default local port for a standalone Tor SOCKS service.
  • 127.0.0.1:9150 — default local port when Tor Browser is running.
  • 127.0.0.1:1080 — local port opened by the SSH dynamic-forward command in this guide.
  • socks5h:// — curl scheme that delegates hostname resolution to the proxy.
  • socks5:// — resolves the hostname locally before connecting; useful only when you specifically want that behavior.

If a client refuses to connect, check the port first, then confirm the proxy process is still running.

When a public SOCKS5 proxy is the wrong choice

Free public SOCKS5 endpoints are listed in many places, but availability and reliability vary widely. Common failure modes include timeouts, throttled bandwidth, and endpoints that disappear between requests. Because the operator is unknown, you also cannot assume the connection is private.

Two rules keep the risk bounded:

  1. Keep HTTPS on so payloads stay encrypted end to end.
  2. Never send passwords, session tokens, or personal data through an endpoint you do not control.

For repeatable work, a Tor service or an SSH tunnel to a machine you own is the safer default. If you do experiment with public lists, test each endpoint before relying on it and expect a high failure rate.

Using the proxy from a scraper

Once either local proxy is running, point your scraper at the same host and port. The browser-based Selenium example in our proxy guide shows how to pass a SOCKS5 endpoint into a WebDriver session. The same pattern applies to other HTTP clients: supply the proxy URL, keep the tunnel process alive, and verify the exit IP before running a large job.

Frequently asked questions

Is a free SOCKS5 proxy actually free?

Tor and an SSH tunnel to a server you already own cost nothing extra beyond your existing hardware and connectivity. Public SOCKS5 lists are free in the sense that no one bills you, but you pay in reliability and trust: endpoints may be slow, offline, or run by an operator you cannot identify.

Why does curl need socks5h:// instead of socks5://?

The socks5h:// scheme asks the proxy to resolve the destination hostname, so DNS lookups happen on the proxy side. With plain socks5://, curl resolves the hostname locally before connecting, which can leak the destination name outside the tunnel.

How do I know the proxy is working?

Compare the IP returned by the proxied request with the IP returned by a direct request. If they match, traffic is not going through the proxy. If the proxied request fails entirely, the proxy process is probably not running or the port is wrong.

Does a SOCKS5 proxy encrypt my traffic?

No. SOCKS5 forwards connections but does not encrypt application data by itself. Keep HTTPS enabled, and avoid sending credentials or sensitive information through any proxy you do not control.

curl --proxy socks5h://127.0.0.1:9050 \
 https://api.ipify.org && echo
curl https://api.ipify.org
curl --proxy socks5h://127.0.0.1:1080 \
 https://api.ipify.org