Socks Proxy List - Free Socks5 Proxy

$0.80 per IP per month on the 10-proxy plan, billed yearly. That is $7.98 a month, or $9.98 if you pay monthly. The 50-proxy plan works out at $0.64 per IP yearly, and the 100-proxy plan at $0.48.

Billing is per IP, with no traffic count behind it, so a busy month costs what a quiet one costs. The 3-day trial with 50 proxies is $3.98, and every paid plan carries a 15-day money-back guarantee.

Static. The address stays the same from one request to the next, which is what a login session, a rank check or an antidetect browser profile needs. You can ask for a new list every 10 days.

For a different IP on each request, take the rotating product instead of this one.

Shared, and private in the sense that matters when a site looks at where an address came from: the pool is paid and none of the addresses appear on public free lists. Another customer may hold the same IP at the same time, which is why it costs $0.48 a month rather than the $5 to $10 a dedicated SOCKS5 IP usually runs.

A list of static IP addresses with the SOCKS5 port and a login. The pool holds 107 addresses in 107 subnets across 34 countries, and the 10-proxy plan draws from the same pool as the 100-proxy plan: nothing is held back for the bigger order.

You choose the countries at checkout, then copy the addresses into whatever you are running. Once the payment clears the list sits in your client area and the addresses answer.

Addresses that share a network prefix get blocked as one unit. When 100 SOCKS5 proxies come from five subnets, one firewall rule ends the whole plan. Packs like that exist because subnets cost the vendor money. Ours sit one per subnet: a range ban takes out one proxy and the other 99 keep working.

The network status table at the bottom of this page shows the current spread.

A subnet is a range of addresses with a shared network prefix, written like 192.0.2.0/24. Firewalls and reputation services treat it as a unit, which is why a SOCKS5 proxy sitting in a busy /24 gets blocked without doing anything itself.

Neither. You pay per SOCKS5 IP per month and the bytes do not appear on the invoice. A scraper that pushes 2 TB pays what one pushing 2 GB pays. Stay inside normal use and do not resell the proxies.

SOCKS5 is port <b>3000</b> and HTTP is port <b>2000</b>, on the same address. A tool that only speaks SOCKS5 needs no second purchase and no second list.

Some clients ask for a version number in their proxy settings. Pick 4 or 5 — port 3000 answers both.

Two authentication methods, and you pick one in the client area.

• Username and password: use this when your own IP changes from time to time.
• Whitelist IP: use this when the program cannot send credentials. The 100-proxy plan allows 5 addresses.

You can switch between them at any time.

1. In the client area, choose the countries and copy the SOCKS5 list.
2. Put an IP and port 3000 into your tool.
3. Open http://ifconfig.co through the proxy. If it reports the proxy's address, you are done.

Yes. It is a standard SOCKS5 endpoint with username and password authentication, so requests, Selenium and curl all take it through their usual proxy option. In curl, use <b>--socks5-hostname</b> if you want the DNS lookup to happen at the proxy as well; <b>--socks5</b> resolves the name on your side first.

Public lists are crawled by everyone, including the people who build blocklists, so an address that answers today can be blocked tomorrow. The server behind it is often a machine its owner left open by accident, and it gets closed, firewalled or overloaded within days. We recheck this list every 10 minutes, and entries still disappear within the hour.

Yes. Every address in the paid pool answers SOCKS4 and SOCKS5 on port 3000, so a program that only speaks SOCKS4 can use the same list. The free list above is mostly SOCKS4 today, which is why it carries a version column.

One thing to plan for: SOCKS4 has no username and password fields, so SOCKS4 traffic can only be authenticated by whitelisting your IP in the client area. If you need username and password authentication, use SOCKS5 on the same address; the two protocols share it.

No. Every address forwards TCP only. UDP ASSOCIATE is not available, so QUIC/HTTP3 and UDP-based game or VoIP traffic will not pass. DNS is a separate matter: with <b>--socks5-hostname</b> the proxy resolves the name for you over an ordinary TCP connection, and that works. Use a VPN for anything that insists on UDP.

34 at the moment, and the selector shows how many addresses each one holds. You can spread a plan across several countries or keep it in one, and the mix can be changed every 10 days.

An address from this pool works with any program that supports SOCKS5, Telegram included, and we do not block that traffic. What we cannot promise is that Telegram's own checks will accept a data center address: those checks change often, and shared IPs trip them more often than private ones do. Try it on the 3-day trial before you commit to a month.