Loading page content.
Raw SOCKS5 endpoints with UDP and remote DNS, for everything that is not an HTTP request.
Starting price
$2.50/IP/wk
per IP, week, from 1 IP. Falls to $1.50/IP/wk at 250 IPs.
Every account starts with 50 MB of free residential bandwidth. No card is required to test the network.
How it works
SOCKS5 works a layer below an HTTP proxy. It authenticates, accepts a CONNECT or a UDP ASSOCIATE, and then forwards bytes without looking at them — so it carries any TCP or UDP protocol, and there is nothing in the path that could add, strip or rewrite a header.
SOCKS5 forwards TCP and UDP untouched, which is what torrent clients, mail transfer agents, game traffic and in-house protocols need from a proxy. Each endpoint is a dedicated address with both user:pass and IP-whitelist auth, and no header rewriting anywhere in the path. Throughput is unmetered for the length of the lease.
The client greets the proxy, authenticates with a username and password, and names a destination. From that point the proxy is a pipe. It has no idea whether it is carrying HTTP, SMTP, BitTorrent or something you wrote yourself.
UDP ASSOCIATE opens a datagram relay on the same endpoint, which is what game traffic, DNS, QUIC-adjacent tooling and torrent peer discovery need and what an HTTP proxy fundamentally cannot provide.
Use the socks5h scheme rather than socks5 and hostnames are resolved at the endpoint. With plain socks5 your own resolver sees every hostname and geo-aware CDNs answer for your real location, which quietly defeats the point of the endpoint.
Each endpoint is provisioned with either residential or datacenter egress. That choice is per endpoint, so a single account can run a residential SOCKS5 for one workload and a datacenter one for another.
The honest limitation: SOCKS5 is a transport, not a disguise. It does not manage cookies, rotate anything, or make a datacenter address look residential. If your problem is being blocked rather than being unable to carry the protocol, the answer is a different egress class, not a different proxy protocol.
Volume ladder
Tiers are a step function, not interpolation: the greatest break at or below your quantity wins and every unit bills at that rate. They apply automatically at checkout — there is no code to enter and nothing to negotiate.
| Quantity | Unit price | Saving | Order total | Order at this tier |
|---|---|---|---|---|
| 1 IP and above | $2.50/IP/wk | Entry rate | $2.50 | Order |
| 5 IPs and above | $2.38/IP/wk | Save 5% | $11.90 | Order |
| 10 IPs and aboveMost popular | $2.25/IP/wk | Save 10% | $22.50 | Order |
| 25 IPs and above | $2.13/IP/wk | Save 15% | $53.25 | Order |
| 50 IPs and above | $2.00/IP/wk | Save 20% | $100.00 | Order |
| 100 IPs and above | $1.75/IP/wk | Save 30% | $175.00 | Order |
| 250 IPs and aboveBest value | $1.50/IP/wk | Save 40% | $375.00 | Order |
Totals are what checkout charges for exactly that quantity. Buying past a break lowers the rate on every unit, not only the ones above it. Price a custom quantity in the calculator.
Specification
Everything a reader needs to decide whether this product fits their stack, on one screen and in one table.
| Property | Value |
|---|---|
| Rotation | None. The endpoint is dedicated for the lease; residential or datacenter egress is chosen at checkout |
| Sticky duration | The whole term. The address does not move |
| Targeting | Egress class and country, set per endpoint at checkout |
| Protocols | SOCKS5 with UDP ASSOCIATE and remote DNS on port 1080, plus HTTP and HTTPS via CONNECT on 8080 and 8443 on the same address |
| Concurrency | Unlimited TCP connections and UDP flows |
| Bandwidth policy | Unmetered throughput for the length of the lease |
| Authentication | Username and password, plus up to 10 whitelisted source addresses |
| Order size | 1 IP to 1,000 IPs per order, in steps of 1 |
Integration
The credential is a host, a port and a pair. What matters is the scheme: socks5h rather than socks5 in a URL, and the equivalent Proxy DNS option in a GUI client.
fp_a41c9dsocks5h://
The h resolves DNS at the proxy. Plain socks5:// leaks every hostname to your local resolver and breaks country targeting.
fp_a41c9d
The credential id for this endpoint.
198.51.100.62:1080
The dedicated endpoint. Ports 8080 and 8443 on the same address speak HTTP and HTTPS for clients that need it.
UDP ASSOCIATE
Enabled by default on the same port. No separate credential and no extra charge.
# socks5h, not socks5 — the h is what makes the proxy resolve DNS.
curl -x socks5h://fp_a41c9d:Wm7pQx2ThBnR4kVz@198.51.100.62:1080 \
-s https://api.fleetproxy.com/v1/ipTargeting
Two decisions, both made at checkout: what the traffic should look like when it exits, and where from.
| Control | How it is set | Notes |
|---|---|---|
| Egress class | Checkout selection | Residential or datacenter, per endpoint. This is the choice that decides how the address is scored. |
| Country | Checkout selection | From the countries with inventory in the chosen egress class. |
| Protocol | Same endpoint | SOCKS5 on 1080 and HTTP/HTTPS on 8080/8443 share one address and one credential. |
| Destination family | IPv4 and IPv6 | Both are reachable from the same port; the endpoint resolves and connects on your behalf. |
Countries where SOCKS5 endpoints can be provisioned. The egress class you choose at checkout decides which inventory the address comes from.
See every country and city with live inventory — counts are the addresses published for that market, not a global total repeated on every page.
Use cases
Four workloads where this product is the right answer rather than a workable one.
BitTorrent needs UDP for peer discovery and a proxy that does not touch the payload. SOCKS5 with UDP ASSOCIATE is the only arrangement that works properly; an HTTP proxy silently breaks half of it.
Real-time protocols are UDP-first and latency-sensitive. A dedicated endpoint with unmetered throughput and no rewriting in the path keeps jitter attributable to the network rather than to us.
In-house binary protocols, database clients, message brokers and anything else with a socket. If it can dial a SOCKS5 proxy, it works here without a shim.
SMTP, IMAP and POP3 over a dedicated address whose reputation is yours. HTTP proxies cannot carry these protocols at all.
Browse every use case for the full breakdown, including the products that suit each one.
Compare
The two nearest products in the catalogue, and the conditions under which each of them is the better purchase. Buying the wrong class costs more than buying the wrong volume.
$2.00/IP/wk
Choose dedicated datacenter IPv4 instead if everything you run is HTTP. It is the same dedicated, unmetered, never-rotating address for less per week — and it speaks SOCKS5 as well, so you are paying the premium here only for the protocol guarantees and the UDP support.
$3.50/IP/wk
Choose static residential instead if what you actually need is an ISP-registered identity for web traffic. SOCKS5 endpoints are sold for protocol coverage; they do not by themselves make an address look like a home connection.
Compare all eight proxy types on identity, rotation, targeting and billing, or price them side by side.
Questions
Pulled from the help center and filtered to the questions this product actually raises.
Yes, on port 1080 with username and password authentication. Use the socks5h scheme rather than socks5 so DNS resolves at the proxy — otherwise your local resolver sees every hostname and geo-aware CDNs resolve against your real location, which defeats country targeting. Port 8080 handles HTTP and HTTPS via CONNECT.
You can add an IP whitelist to any credential, but password authentication is still required alongside it — the whitelist narrows who may use the credential, it does not replace authentication. Whitelists are per-credential rather than per-account, so adding an address to one credential does not add it to the others. A changed office IP or a new CI runner is a common cause of sudden 407s.
Residential IPs are addresses assigned by consumer ISPs to real subscriber connections, so targets see an ordinary visitor; they cost more and add 200–900ms of latency. Datacenter IPs come from hosting providers, are roughly twenty times cheaper per gigabyte and much faster, but are trivially identifiable and filtered by any site that cares. Mobile IPs are carrier-assigned 4G/5G addresses shared by thousands of subscribers, which makes them the hardest to block and the most expensive. Start with datacenter on undefended targets and residential everywhere else.
No. Create an account and claim the 50 MB free trial of rotating residential bandwidth — no payment method, no call. That is enough to run a few hundred requests against your real target and measure the success rate before you spend anything.
No. We meter volume — bytes up, bytes down, request counts, success and failure counts, mean latency and exit country, aggregated per plan per hour. We do not record destination hostnames, URLs, headers or traffic content, and the usage tables have no column capable of holding them. Connection metadata such as your account's login IP is retained as described in the privacy policy.
No. Purchased bandwidth stays on the account for as long as the account is open and in good standing. Most of the industry expires unused traffic at the end of the billing period, which turns a bursty workload into 30–40% waste; we do not, and that is a policy commitment rather than a promotion.
Something not covered here? Read the full help center or ask the support team.
Start on 50 MB of free residential bandwidth, then buy from $2.50/IP/wk. Volume tiers apply automatically, and there is no contract to sign.
No card required for the trial. Cancel or downgrade at any time.