PHproxies sells access to a pool of residential proxies. Your requests are routed through real residential IP addresses, so websites see a regular home connection instead of a data-center server. You can target a country, region or city and choose between rotating IPs and sticky sessions. Plans are priced by the number of concurrent connections per IP you can keep open — see Plans & connections below.

Common legitimate uses are web data collection of public information, price and ad verification, SEO monitoring, brand protection, QA and localization testing, and accessing your own accounts from different locations. Everything you do must follow our Acceptable Use Policy and the law — see the next question.

Spam, fraud, carding, credential stuffing, account takeover, DDoS, hacking or scanning systems you do not own, and any illegal content or activity are strictly forbidden. Outgoing e-mail ports (25, 465, 587) are blocked. Violations lead to immediate termination without a refund. Read the full Acceptable Use Policy.

When a free trial is available it is granted automatically after you verify your e-mail address, once per person. A trial is a small package with a short validity and a small traffic allowance, so you can test locations and your own tools before buying. Extra connections cannot be bought for a trial.

Plans are sold by concurrent connections per IP: how many proxy connections each of your whitelisted IP addresses may keep open at the same time, for the validity shown on the plan (for example 30 days). Each plan card also lists its other limits — how many IPs you can whitelist, sticky sessions and, if the plan has one, a total connection limit or a traffic allowance.

One connection that is open through the proxy at a given moment — one SOCKS5 session or one HTTP / HTTPS (CONNECT) tunnel. A scraper running 50 threads usually needs about 50 connections; a browser can open 6 or more connections for a single page. A connection is counted from the moment it opens until it closes, so close connections you no longer use (or lower keep-alive time) to free the slot.

The limit applies to each whitelisted IP separately. With a plan of 100 connections per IP and 3 whitelisted IPs, each of the 3 machines can keep up to 100 connections open at the same time. Some plans also have a total limit for the whole package — when they do, it is shown on the plan card.

New connections from that IP are refused until some of the open ones close — SOCKS5 clients get a connection not allowed by ruleset error and HTTP clients get status 429 with the message too many connections. Connections that are already open are not affected. Lower the number of threads, close idle connections, whitelist the extra machines, or buy extra connections.

Yes. On My proxy, open your package and click Add connections, then pick a pack. The extra connections are added to every IP of that package immediately and last until the package's expiry at the time you buy them — renewing the package later does not extend them, so buy them again after a renewal if you still need them. Extra connections are not available for the free trial or for expired packages.

Yes. Every purchase of a plan creates a separate package with its own whitelisted IPs, limits and expiry; renewing adds time to an existing package instead. You can whitelist the same IP address on several of your packages: each package has its own proxy servers, so connect to the endpoints of the package you want to use.

Plans are sold by connections, not by the gigabyte. If a plan includes a traffic allowance it is shown on the plan card, and that package stops when the allowance is used up; otherwise you are not charged per gigabyte. We still measure traffic for statistics, abuse prevention and fair use under our Acceptable Use Policy.

1. Create an account and verify your e-mail address.
2. Top up your wallet and buy a plan — it becomes a package.
3. Open My proxy and whitelist the public IPv4 address of every machine that will connect.
4. Copy an endpoint (IP:port) or build a targeted proxy string with the Targeting builder.
5. Keep the number of open connections from each machine within your connections per IP.

Authentication is done by IP whitelist. Only connections coming from an IP address you added on the My proxy page are accepted. There is no password — anything you put in the password field is ignored. The username is only used to pass targeting options (country, city, session).

The public IPv4 address of the machine that opens the connection to our proxy. Visit api.ipify.org from that machine to see it. Private addresses (192.168.x.x, 10.x.x.x…), IPv6 and ranges are not accepted. If your ISP changes your IP, update it on the My proxy page.

SOCKS5 and HTTP / HTTPS (CONNECT). With SOCKS5, use socks5h:// so that DNS is resolved on the proxy side and your real location does not leak through DNS.

Use the Targeting builder on the My proxy page. It generates a username such as country-us-city-losangeles. Country codes are ISO-2 (us, gb, de…); regions and cities are written in lower case without spaces or punctuation.

Rotating gives you a new IP for every new connection. Sticky keeps the same IP for as long as the session lives: turn on Sticky session in the builder, and every username with the same session id is routed through the same residential IP until the session expires or the IP goes offline.

Yes. In the Targeting builder turn on Sticky session and enter how many sessions you need (up to the limit of your plan). You get a list with one proxy per line, each with its own session id, ready to copy or download as a .txt file.

No. Residential IPs belong to real devices that come and go. Geo-targeting is best effort: the IP pool for a small city may be empty at a given moment, a sticky session may change IP before it expires, and third-party geolocation databases may disagree with the location we report. This is normal for residential proxies and is not a reason for a refund.

Top up your wallet with cryptocurrency (for example USDT, BTC or LTC, depending on what is enabled), then use the balance to buy a plan, renew a package or buy extra connections. Deposits are credited automatically once the payment is confirmed on the blockchain.

Always send the exact amount, in the exact coin and on the exact network shown on the invoice. Underpayments are credited only for the amount actually received once confirmed. Payments sent on the wrong network, to an expired invoice or to a wrong address may be permanently lost — blockchain transactions cannot be reversed and we are not responsible for such losses.

No. All purchases, deposits and wallet balances are final and non-refundable under any circumstances, including unused connections, unused days or traffic, extra connections that end with the package, dissatisfaction with locations, blocked target websites, and accounts terminated for policy violations. Please use the free trial (when available) before you buy. See the Refund Policy.

No. Wallet balance can only be used to buy services on PHproxies. It cannot be withdrawn, exchanged or transferred to another account.

The proxies of that package stop working and its whitelisted IPs are removed (suspended packages too), so the addresses are free to use again. After you renew, add your IPs again on My proxy. Your other packages are not affected. Extra connections end at the expiry they were bought for. If the plan includes a traffic allowance, the package also stops when the allowance is used up.

The proxies of that package stop working and its whitelisted IPs are removed (suspended packages too), so the addresses are free to use again. After you renew, add your IPs again on My proxy. Your other packages are not affected. Extra connections end at the expiry they were bought for. If the plan includes a traffic allowance, the package also stops when the allowance is used up.

Both upload and download bytes passing through the proxy are counted, including protocol overhead, TLS handshakes, retries and failed or blocked requests that transferred data. Your dashboard shows usage per day. Traffic only limits a package when its plan includes a traffic allowance.

Both upload and download bytes passing through the proxy are counted, including protocol overhead, TLS handshakes, retries and failed or blocked requests that transferred data. Your dashboard shows usage per day. Traffic only limits a package when its plan includes a traffic allowance.

For security reasons, access to financial and government-related websites is strictly prohibited through our proxies. This restriction is part of our compliance with local laws and regulations. Additionally, sending emails through our proxies is not allowed, and SMTP port 25 is blocked.

Usually because the IP you connect from is not whitelisted, the package has expired, or that IP already has as many open connections as its plan allows (HTTP clients then get status 429 — too many connections). Check the My proxy page: your current IP must appear in the whitelist of an active package, and your tool must not open more connections per IP than the plan allows.

Target websites decide on their own whether to serve a request. Residential IPs are shared and may already be rate-limited or flagged by a particular site. Use sticky sessions, lower concurrency and realistic request headers. We cannot guarantee access to any particular website.

Up to your plan's concurrent connections per IP from each whitelisted IP — plus any extra connections you bought for that package. If the plan also has a total limit for the package, all IPs together cannot go above it. New connections above the limit are refused until older ones close; you can see the limits of each package on My proxy.

No. We work hard to keep the network available, but the service is provided as is without any uptime guarantee. Maintenance and outages do not entitle you to a refund or compensation.

We do not record the content of your traffic. We do keep technical metadata needed to run, bill and protect the service — such as your whitelisted IPs, traffic volume, request counts and aggregated destination hostnames. See the Privacy Policy.

Use a unique password and turn on two-factor authentication in Account → Two-factor authentication. Never share your account; you are responsible for everything done through it and through your whitelisted IPs.

Sign in with one of your recovery codes. If you lost them too, open a ticket or contact [email protected] — after verifying your identity we can reset 2FA so you can set it up again.

Open a ticket from your dashboard (Support) or contact [email protected]. Please include your account e-mail and a short description of the problem.