Configure any available plan and add-ons. Pay only for 48 hours.
Try proxiesSOCKS4 support is included with every plan — the same IPs also answer over SOCKS5, HTTP, and HTTPS, so legacy tools don't need a separate list.
SOCKS4 is the 1990s predecessor of SOCKS5: the same blind TCP tunnel — the proxy relays bytes without reading or modifying them — minus everything the fifth version added later. There's no username/password authentication, no UDP, no IPv6, and no remote DNS: your application resolves the hostname itself and hands the proxy a ready IPv4 address.
You need it in exactly one situation: software written before SOCKS5 support became universal and never updated since. Old Windows utilities, self-written bots, tools whose vendor disappeared years ago — none of them are worth rewriting while they still do their job. Before settling on version 4, though, dig through the tool's advanced settings: plenty of applications that claim to be SOCKS4-only actually support v5 and simply default to the older version for compatibility.
There's no separate SOCKS4 product to buy here — every IP in every package accepts SOCKS4, SOCKS5, HTTP, and HTTPS connections on the same port, at no extra charge. A legacy tool runs today, and when you replace it, you change one dropdown in its settings, not your proxy list. Specs are in the adjacent panel; pricing is in the calculator above.
Four proxy protocols — how they differ and when to use each one.
| HTTP | HTTPS | This page SOCKS4 |
SOCKS5 | |
|---|---|---|---|---|
| Traffic encryption | ✕ No TLS to the proxythe proxy connection is unencrypted | ✓ TLS tunnelto our server and the target site | Depends on the application protocolHTTPS traffic remains encrypted | Depends on the application protocolHTTPS traffic remains encrypted |
| Header handling | May add or modify HTTP headers | TunneledHTTP headers inside the tunnel are not modified | Passes application traffic unchanged | Passes application traffic unchanged |
| TCP / UDP | TCP | TCP | TCP | TCP + UDP |
| Username/password auth | ✓ Supported | ✓ Supported | ✕ No password authentication | ✓ Supported |
| Remote DNS resolution | Client-dependent | Client-dependent | ✕ Nothe client resolves the hostname | ✓ Supportedwhen the client sends the hostname to the proxy |
| When to choose it | Web and API traffic, especially with software that supports HTTP proxies | When you need a TLS-encrypted connection to the proxy | Legacy software that only supports SOCKS4 | General-purpose applications, gaming, streaming, and UDP traffic |
| HTTP, HTTPS, SOCKS4, and SOCKS5 are included with every static proxy plan. Rotating plans support HTTP and SOCKS5. Buy now | ||||
Copy the example for your stack, or paste it into your AI coding assistant for help adapting it to your project.
# HTTP or HTTPS proxy curl -x http://login:password@IP:port https://example.com # SOCKS5 curl --socks5-hostname IP:port \ --proxy-user login:password \ https://example.com
import requests proxy = "http://login:password@IP:port" # your proxy from the Dashboard r = requests.get( "https://example.com", proxies={"http": proxy, "https": proxy}, ) print(r.status_code)
import { ProxyAgent } from "undici"; const dispatcher = new ProxyAgent("http://login:password@IP:port"); const res = await fetch("https://example.com", { dispatcher }); console.log(res.status);
$ch = curl_init("https://example.com"); curl_setopt($ch, CURLOPT_PROXY, "IP:port"); curl_setopt($ch, CURLOPT_PROXYUSERPWD, "login:password"); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $response = curl_exec($ch);
Choose a standard format or create a custom one with any field order and delimiter your software requires.
See the FAQ for the ports used by each protocol.
You can automate purchases, renewals, whitelist changes, and proxy list exports. Create an API key in your Dashboard in a couple of clicks.
Claude, Cursor, and other agents buy proxies, renew plans, and export updated proxy lists through an access token you create in your Dashboard. See how it works.
Per-IP prices shown are for the largest package size. Get an exact quote in the calculator above.
| IP | Country | Port | Protocol | |
|---|---|---|---|---|
| 199.187.210.54 | US | 4145 | SOCKS5 | |
| 159.192.139.42 | TH | 5678 | SOCKS4 | |
| 60.217.64.237 | CN | 35292 | SOCKS4 | |
| 185.216.18.138 | RU | 44550 | SOCKS4 | |
| 147.45.60.246 | RU | 1082 | SOCKS4 | |
| 181.57.178.146 | CO | 1080 | SOCKS4 | |
| 114.108.177.104 | KR | 60984 | SOCKS4 | |
| 27.147.218.182 | BD | 1080 | SOCKS4 | |
| 152.53.183.107 | DE | 8081 | SOCKS5 | |
| 193.105.62.11 | UA | 58973 | SOCKS4 |
A few service metrics—and feedback from our customers.
I am thankful to the service creators for user-friendly interface. As for proxy-servers they are rather fast and of high quality.
Prompt service, as well as a large number of different tariff plans. You can subscribe to several packages at the same time to use them via API. I bought unlimited proxies with rotation.
I took proxies for Ukraine. I need proxy servers for my social networks. The admins advised me how to use proxies effectively in order not to ban my accounts. The proxies themselves work well and the prices are as adequate as possible.
KeyCollector started to ban free proxies. So I started looking for paid proxies. I compared prices and chose this service. I was looking for IPv4 proxies, they are a bit cheaper than the competitors. In general, I like everything, if there are any questions, the support immediately solves them. Very convenient!
Can't find your answer? Message us in live chat — real humans reply.
No — SOCKS4 is a connection mode, not a separate product. Every IP in a package answers over SOCKS4 on the same port that serves SOCKS5, HTTP, and HTTPS: enter ip:port in the bot and it runs. When you eventually replace the tool, switch its protocol setting to SOCKS5 — the list, the whitelisting rules, and the plan stay exactly as they were.
IP whitelisting — and it closes the gap the protocol left open. A bare SOCKS4 server is defenseless by design: there's no authentication in the protocol at all, so anyone who finds the address can route traffic through it. Our proxies respond only to source IPs you've added in the Dashboard — whitelisting is mandatory on every plan — so the missing password never comes into play. Add your machine's IP and that's the entire security setup; there's nothing to configure inside the protocol itself.
Almost always DNS or IPv6 — SOCKS4 predates both. The client has to resolve the hostname itself and pass the proxy a ready IPv4 address, so if your application can't resolve the name locally, or the target only resolves to an IPv6 address, the connection dies before it starts. Some tools work around the DNS half with the SOCKS4a extension, which sends hostnames to the proxy, but client support for it is inconsistent. If a site works over SOCKS5, that's your fix: the same IPs, and version 5 resolves names on the proxy side — setup details are on the SOCKS5 page.
Because software outlives protocols. SOCKS5 has been the standard since 1996, yet tools written before their authors adopted it are still running in production in 2026 — and they keep SOCKS4 alive, not any technical advantage. The rule is short: new project — SOCKS5, always; a working legacy tool — SOCKS4 as its compatibility mode, on the same addresses, and nothing needs rewriting.
A different proxy type may be a better fit for your use case. All products use the same Dashboard and support team.
An IP reserved exclusively for you, available from a single IP. Speeds of up to 500 Mbps per proxy.
Learn moreStatic ISP-registered residential IPs for use cases where network origin matters.
Learn morePay per request and access the full 100,000+ IP pool through a single gateway. Built for web scraping and API workloads.
Learn moreSOCKS5 with UDP support — for gaming, streaming, and VoIP.
Learn moreWe can sign a contract and provide all the documents your accounting team needs. Most business orders are activated within 24 hours of your request.