Get Started →
Guide 8 min read

922 S5 Proxy Setup: From First IP to a Working Profile

922 S5 works differently from metered providers, and the setup reflects that. You are not provisioning a bandwidth plan — you are buying addresses and assigning them. This guide covers the whole path: first purchase, credential format, profile assignment, verification, and the habits that keep bought IPs useful for months.

ML
Mark Lev
Network operations lead. Has been running residential SOCKS5 proxy stacks since 2019.
In this article
  1. Buying the first block of IPs
  2. One IP, one identity
  3. Connecting over SOCKS5
  4. Verifying an exit properly
  5. IP hygiene that keeps addresses alive
  6. Scaling without wasting money
  7. FAQ

Buying the first block of IPs

Start from identity count, not traffic. Every profile, account or worker that must look like a separate person needs its own address — that number is your order size. Prices start at $0.07 per IP with volume tiers below that, and code OPEN30 takes 30% off a first order.

There is no reason to over-buy. Balances never expire, and top-ups later cost the same rate, so a first order should be small enough to test honestly and large enough to be real.

Checkout is crypto only — USDT TRC20/BEP20/ERC20, BTC, LTC, TRX, ETH, XMR. Send the exact amount shown and the balance credits automatically after confirmation, usually within minutes.

One IP, one identity

This is the rule the whole model rests on. A purchased address does not rotate, which is exactly why it is valuable — and exactly why sharing one across unrelated accounts destroys that value. Two accounts on one IP are two accounts a platform can link.

Keep a mapping somewhere durable: profile name, IP, purchase date, platform. It sounds bureaucratic until the day an account gets flagged and you need to know what else touched that address.

Connecting over SOCKS5

SOCKS5 is the default here because it carries any TCP traffic and adds no proxy headers. HTTP(S) shares the same login if a legacy stack needs it.

Verifying an exit properly

Test every IP before it carries anything that matters. Check the reported country and city against what you bought. Check that DNS resolves at the exit rather than on your machine — a local resolver undoes the whole exercise. Check WebRTC in the browser profile, because a leaked local address is the single most common reason a carefully built profile gets linked.

An IP that fails any of these is worth reporting rather than working around. Support reviews and replaces addresses; burning a profile on a bad exit costs far more.

IP hygiene that keeps addresses alive

Scaling without wasting money

Because nothing expires, scaling is incremental by default. Add IPs as identities are created rather than pre-buying a quarter's worth. Use metered residential traffic for the crawling parts of the pipeline — those are volume-bound, not identity-bound, and paying per IP for them is the wrong tool. Move anything that must survive a platform review onto static ISP.

The mature setup is a mix: owned IPs for identities, metered traffic for collection, static ISP for the two or three accounts that cannot be replaced.

FAQ

Is there a 922 S5 client to download?

No. Setup is credential-based and works in any tool that speaks SOCKS5. Treat 'download' links elsewhere as untrusted reuploads.

Do my IPs expire if I stop using them?

No. They stay on the balance indefinitely.

Can I change an IP's country later?

An address belongs to its region. To move markets, buy an IP in the new one — the old address stays available for its own profile.

Is KYC required?

No. Email registration and crypto checkout, nothing else.

Get residential SOCKS5 in 2 minutes

922Proxys5: 350M+ residential IPs, 200+ countries, SOCKS5 + HTTP(S) on the same credentials, crypto checkout, balance never expires. Code OPEN30 = 30% off.

View Pricing →

Related reading