Use case · QA and geo-testing
Proxies for QA and geo-testing
Check your own site with the requested network route, browser settings and expected result recorded for each test.
The job
What this actually is.
Use a country-targeted proxy to test your own site or app against its expected behaviour. Check currency and tax display, translations, hreflang targets, consent, available payment methods, CDN responses and redirects. A passing HTTP status is only the start: verify the content and interaction your test requires.
Compare country settings and network location as separate inputs. Record the requested proxy pool and country alongside locale, timezone, viewport, account state and saved site preferences. Keep the browser settings fixed when comparing routes, then change one input at a time. Record the country requested separately from the market the site displays; an echo IP does not by itself verify the exit country.
For a first-visit check, create a clean browser context with its own cookies and storage. For a returning-user journey, preserve the intended context and test-account state. Configure the Playwright browser connection on that context. For a manual pass, set the proxy in Chrome with an extension, in a browser profile kept for testing. Rotating the network connection does not clear cookies, reset consent or make each request a new visitor.
Which pool
Mobile or residential for this job.
Choose residential when the test needs a peer-network connection in a country currently available in that pool. Peer devices use a mix of home broadband and mobile connections; a residential route does not guarantee a particular access network. Check live availability before the run. Both pools are shared and use the same GB balance.
Choose mobile 4G/5G when the test specifically needs a carrier-network exit. Set the browser or device separately: the proxy does not turn a desktop browser into a phone or reproduce a phone’s radio or wifi conditions. Keep viewport, user agent and other browser inputs explicit when testing layouts or device behaviour.
Mobile 4G/5G proxies by the GB · Residential proxies by the GB · Check countries online now
Settings
Rotation, and the username that sets it.
| Mode | Username | Use it for |
|---|---|---|
| Sticky sessionFor related permitted steps that need proxy-session continuity. Keep the session name with the intended browser context and staging account. The same device is used while available; its IP can still change, and application state remains a separate control. | USERNAME-mbl-fr-sid-run42-rot-sticky | For related permitted steps that need proxy-session continuity. Keep the session name with the intended browser context and staging account. The same device is used while available; its IP can still change, and application state remains a separate control. |
| Per-connection rotationFor checks that do not need a continuing proxy session. Addresses can repeat, and requests may reuse an existing connection. Use a fresh browser context when the test requires first-visit state. | USERNAME-peer-it-rot-ondemand | For checks that do not need a continuing proxy session. Addresses can repeat, and requests may reuse an existing connection. Use a fresh browser context when the test requires first-visit state. |
| Timed rotation (60-minute example)For tests designed to tolerate scheduled route changes. A timer does not wait for a page, form or test case to finish. Keep multi-step journeys on a named sticky session when they need continuity. | USERNAME-peer-it-rot-auto60 | For tests designed to tolerate scheduled route changes. A timer does not wait for a page, form or test case to finish. Keep multi-step journeys on a named sticky session when they need continuity. |
USERNAME stands for the account part of your username; it and the password appear in the dashboard after a fulfilled purchase. Swap the two-letter country code for an available market. Every token is listed in the docs.
# Two independent HTTP GET checks using the same named proxy session
# Replace the staging URLs with pages you own or have permission to test
curl --disable --silent --show-error --fail-with-body --noproxy '' \
--connect-timeout 5 --max-time 15 -x "http://gw.portproof.org:7000" \
--proxy-user "USERNAME-mbl-fr-sid-run42-rot-sticky" \
-H "Accept-Language: fr-FR" -o step1.html "https://staging.example.com/"
curl --disable --silent --show-error --fail-with-body --noproxy '' \
--connect-timeout 5 --max-time 15 -x "http://gw.portproof.org:7000" \
--proxy-user "USERNAME-mbl-fr-sid-run42-rot-sticky" \
-H "Accept-Language: fr-FR" -o step2.html "https://staging.example.com/checkout"
# This separate request reports only its own exit address
curl --disable --silent --show-error --noproxy '' \
--connect-timeout 5 --max-time 15 -x "http://gw.portproof.org:7000" \
--proxy-user "USERNAME-mbl-fr-sid-run42-rot-sticky" "https://api.portproof.org/v1/echo-ip"These GET checks do not share browser cookies, run JavaScript or submit a checkout. A sticky session reuses the device while available; its IP can still change. Use a browser context for an actual user journey. Replace USERNAME with your account value and use an interactive terminal for the password prompts; the transfer timeout does not bound password-entry time.
Cost
How to think about the GB.
Measure a representative permitted suite before choosing how many GB to buy. Include the pages, resources, redirects and retry policy needed by the test. Plan bandwidth from that sample, then compare it with account usage after the meter refreshes. Client counters and the account meter do not necessarily include the same bytes; read what counts as proxy traffic before treating them as equal.
Keep interrupted steps separate from application assertions. A sticky session keeps the same device. The carrier may still change the IP of that device. A peer device can disconnect too. For reads safe to repeat, use bounded retries that preserve the test conditions. Do not automatically replay a form submission or purchase after a connection failure.
Traffic is EUR 4.50 per GB for a small order and EUR 2.50 per GB at the largest step, on either pool. The paid trial is 0.5 GB for EUR 2.90, once per customer and subject to eligibility. View pricing and traffic validity.
Limits
What we will not help with.
Test your own properties, or ones you have permission to test. Use authorised test accounts and the relevant provider’s test mode for payment or integration checks. Load testing through the gateway is not allowed: the pools are shared, and a flood harms other customers’ runs as well as the destination.
Read the acceptable-use policy before ordering. You accept it at checkout.
Start