SOCKS5 Residential Proxies

Do Tensor Proxies support SOCKS5?

Yes. HTTP and SOCKS5 are supported on the Datacenter, Static Residential ISP, and Rotating Residential ISP packages, using the same username and password. Nothing is enabled per order and nothing costs extra, so you can move a proxy list between protocols without reissuing credentials.

Practically, that means one purchased pool covers a mixed stack: a Scrapy job on HTTP, a fingerprint browser profile on SOCKS5, and a desktop client that only speaks SOCKS, all pointed at the same IPs.

SOCKS5 vs HTTP proxies — which should I use?

Use HTTP when your client is a browser or an HTTP library and you want per-request control. Use SOCKS5 when the traffic is not plain HTTP, when the client only offers a SOCKS field, or when you want the proxy to pass bytes through without touching headers. For ordinary web requests the difference in behaviour is small; for anything else, SOCKS5 is the safer default.

One practical detail: an HTTP proxy sees and can modify request headers, while SOCKS5 does not inspect what it forwards. If you are debugging why a target behaves differently through a proxy, switching protocols is a fast way to isolate whether header handling is involved.

What is an HTTP and SOCKS5 proxy pool?

A pool is simply the set of proxies you hold, addressed as a list rather than a single endpoint. Because both protocols run on the same credentials here, one purchased list is simultaneously an HTTP pool and a SOCKS5 pool — you decide per connection which protocol to speak, and you decide how to cycle through the IPs.

Pools are sold in blocks of 25. Static Residential ISP is $15 per 25 proxies ($0.60 each) and Datacenter is $8 per 25 ($0.32 each, dropping to $0.14 at 5,000+), so scaling the pool is a quantity change in the purchase flow, not a plan migration.

Is this a private proxy pool or a shared one?

Static Residential ISP and Datacenter proxies are dedicated: the IPs in your list are assigned to your order, not rotated among other customers. That is what people usually mean by a private proxy pool — you know exactly which addresses you hold and how hard each one is being used.

The shared-pool model is the rotating residential product, where a gateway maps each request to an IP drawn from a large common pool. That package is currently sold out, so every purchasable Tensor Proxies package today is a dedicated list.

How do I buy SOCKS5 static ISP proxies?

Buy the Static Residential ISP package — there is no separate SOCKS5 product to select. Choose your quantity in the purchase flow, allocate it across countries, and check out through Stripe. The credentials that arrive work over SOCKS5 and HTTP alike, so the protocol decision happens in your client after delivery, not at checkout.

Minimum order is 25 proxies at $15, and the static ISP rate stays flat at $0.60 per proxy no matter how large the order gets.

How do I configure SOCKS5 with the delivered credentials?

Split the delivered line into its four parts and feed them to your client's SOCKS5 fields. In curl that is --proxy socks5://USERNAME:PASSWORD@IP:PORT; in Python requests it is a proxies dict using the socks5:// scheme; in Playwright or a fingerprint browser it is the proxy server field with username and password entered separately. No SDK, gateway, or whitelist step is involved.