QA · Localization · Checkout testing

Proxies for QA and Geo Testing

Geo testing proxies let your team see your own website, app or checkout the way a visitor in the United States sees it: the currency, tax, consent banner, redirects, CDN edge and content you serve to US traffic. A residential ISP address gets the experience a customer gets, which a test from a cloud server may not.

See pricingarrow_downward All use casesapps

Why ISP Addresses Suit Testing

public

A US visitor's view

Check currency, tax, shipping and consent banners for US visitors from wherever your team is.

router

Not a data-center address

Your own bot protection and CDN treat ISP traffic like a customer's, so tests match production.

push_pin

Repeatable

A static address gives every test run the same starting point.

code

In your test suite

Set the proxy in Playwright, Cypress, Selenium or curl and run it in CI.

hub

HTTP and SOCKS5

Every address answers both with one login.

inventory_2

Small orders are fine

A few addresses usually cover a QA team.

Pricing

Static US ISP addresses, each with an HTTP and a SOCKS5 port and one login. The price per address depends on how many you order. The order link opens the proxy order form with this use already chosen.

ISP proxy prices per address per month, for qa and geo testing
Addresses	Price per Address	Order
1–19	$1.80/mo	Order
20–49	$1.70/mo	Order
50–99	$1.60/mo	Order
100–299	$1.50/mo	Order
300–499	$1.40/mo	Order
500–999	$1.30/mo	Order
1000+	By quote	Contact us

Setting It Up

1
List what changes by location
Currency, tax, shipping options, consent banners, redirects, language and blocked content.
2
Order with QA and geo testing as the use
A few addresses are usually enough. Keep "QA and geo testing" as the intended use, accept the Acceptable Use Policy and pay.
3
Add the proxy to your tests
Set it per browser context in Playwright or per session in your test tool, and keep the credentials in your CI secrets.
4
Compare against your own location
Run the same test with and without the proxy, and check the differences are the ones you intended.

Where the Line Is

Every order states its intended use and accepts our Acceptable Use Policy. Services used for anything on the right are suspended, and the fees are not refunded.

Fine

check_circleTesting your own website, app or checkout for US visitors
check_circleChecking your CDN, redirects and geo rules
check_circleVerifying consent banners and legal notices shown in the US
check_circleTesting a client's site you are contracted to work on

Not allowed

blockLoad testing or flooding sites you do not own
blockScanning or probing systems you do not own
blockLogging in to accounts that are not yours, or testing leaked passwords
blockSending email or bulk messages through the proxies

Good to Know Before You Order

infoThese are for testing what you own or are hired to test. Security scanning of other people's systems is not allowed.
infoAll addresses are in the United States. We do not offer other countries yet.
infoSOCKS5 over UDP has not been tested on these proxies; test with TCP traffic.
infoCredentials in CI should live in your secrets store, never in the repository.

Questions

Why not test from a cloud server in the US?expand_more

Many sites, including your own CDN and bot protection, treat data-center traffic differently from home connections. An ISP address shows what a customer gets.

Can I test other countries?expand_more

Not with these proxies. Every address is in the United States.

Can I use them for load testing?expand_more

No. They are for checking behavior, not generating load, and load testing sites you do not own is not allowed.

How many do I need?expand_more

Usually one to five for a QA team, unless tests run in parallel from many workers at once.

Guides for This

Other Use Cases

All use cases

Ready to order?

Choose a quantity, confirm the use and pay by card or PayPal. Addresses appear in your dashboard after payment.

Order proxiesarrow_forward