Frequently asked questions

Residential for geography and IP reputation, Residential TLS when a clean residential IP still gets challenged, and the Premium pools when the target refuses ordinary residential exits.

The exits are the same network. Residential TLS additionally rewrites the TLS handshake to match one of 127 profiles captured from real browser builds, and holds that profile for the life of a sticky session.

No. Ludax products are IPv4 today. If IPv6 is a requirement, tell support — demand is what would make it a roadmap item.

Yes. One account and one wallet balance can pay for plans on all four products. Each product has its own plan and its own gateway port, and each plan is valid for 30 days from activation.

Point any tool that accepts a proxy URL at your product's port on gw.ludaxproxy.com — Residential 7777, Residential TLS 9999, Residential Premium 8080 (SOCKS5 on 1080), Residential Premium TLS 8081 — using the username and password from your dashboard.

No, and that is deliberate. Everything is controlled by parameters appended to the proxy password, so there is no library to install or keep updated.

SOCKS5 runs on Residential Premium in normal mode, at gw.ludaxproxy.com:1080. The other products are HTTP and HTTPS only.

Authentication is by username and password on every product.

Send no session token. Rotation per request is the default behaviour.

Append -session- and a 3–24 character token to hold the same exit, and -time- to set the lifetime in minutes — up to 1000 on every product. The default is 10 minutes.

Yes. Change the session token and the next request leaves from a different exit immediately.

On Residential TLS plans, yes — the IP and the pinned profile are held together for the session.

Append -country- and the two-letter ISO code. The residential gateway accepts any ISO 3166-1 alpha-2 code; availability varies by market and over time.

On Residential and Residential TLS, yes, with -city- after -country-, where the locations dataset lists cities, and -state- between them targets a state. Residential Premium targets country and ASN instead, and there is no ZIP-level selector on any product.

No. Inventory changes continuously and any published number would be misleading, so we do not print one.

Prepaid per gigabyte, metered to the kilobyte in both directions. Each plan is valid for 30 days from activation; unspent wallet funds stay on the account.

Cryptocurrency only: BTC, USDT, ETH and others. Balance is credited once the transaction confirms on-chain.

No. Nothing renews automatically and there is nothing to cancel.

Prices may change for future purchases. A change never alters the rate on balance you already hold.

Once traffic has been routed, no — balance is delivered instantly and consumed irreversibly. An entirely unused plan purchased within the last 48 hours is reviewed case by case.

Where a documented platform fault prevented you from using purchased capacity, the affected balance is credited back to your account rather than refunded on-chain.

It stays on the account. Unused balance is not refunded on voluntary account closure.

Traffic content is not stored. Account and billing records, plus the aggregate bandwidth and thread counters needed to meter your plan, are retained as described in the Privacy Policy.

No. Your gateway credentials belong to your account. Never publish them in code repositories or screenshots — the documentation uses placeholders for exactly this reason.

No. It changes the exit address of your request. Cookies, storage, account identifiers, browser artefacts and your own request patterns are unaffected.

Yes. Choose Add a web password on the login page and set one for the account you already use in the bot. Telegram and web access resolve to the same account: the same balance, the same plans, no second wallet. Passwords are stored only as Argon2id hashes and are never held in plain text.

Validate content shape, not just status codes. Then try a sticky session, and if the target inspects handshakes, move to Residential TLS.

City narrowing falls back to country level when capacity is short. Log the exit returned by api.ludaxproxy.com/whoami to see what you actually got.

Residential exits are consumer lines and latency varies by region and line. Premium draws on a separate pool with its own gateway ports.

It is only honoured on Residential TLS plans; on standard plans it is ignored rather than raising an error.

Telegram at @LudaxProxy or email [email protected]. Both reach the same team.

Response time depends on demand. We do not publish a service-level commitment, because we do not operate one.

The exact proxy string with the password redacted, the target URL, the timestamp, and what you expected versus what you got. That is usually enough to reproduce it.