All about proxies
All about residential proxies
Residential proxies route traffic through IPs associated with consumer broadband. They are a practical default when you need many locations and the target is not specifically mobile-only.
How they differ from mobile and datacenter
Residential sits between mobile (carrier) and datacenter (hosting). Use residential for public websites that filter obvious hosting ranges but do not require a mobile ASN.
Location targeting
Set the country in the dashboard before you collect. Tag every stored record with that location so later comparisons stay valid.
Credentials
Use the dashboard values in any client that supports HTTP or SOCKS5. Do not commit passwords to git; load them from environment variables.
Instructions
1. Choose residential on pricing
Select bandwidth and billing period, then complete checkout.
2. Set the market
Open the proxy and pick the location that matches the pages you will request.
3. Run a canary URL
Fetch one public page and confirm language, currency, or layout for that market.
4. Scale the job
Keep session policy documented: sticky for pagination, rotate between independent batches.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://example.comRelated sections
Residential proxies with geo targeting
Pin a dashboard location, fetch a canary page, then clone the job per market.
All about mobile proxies
Carrier-network IPs for workflows that need mobile traffic and dashboard-controlled rotation.
All about datacenter proxies
Static hosting IPs for speed and volume when the destination does not require consumer networks.
How to set up Premip proxies in Selenium
Set the browser proxy to HOST:PORT and supply username and password from the dashboard.
If you still need help, message us on Telegram or email. Include your account email and, if you have one, your order ID.
Message us
Reach support on Telegram, email, phone, or the contact form. Include your account email and, if you have one, your order ID.