Proxies for Sweetwater meet PerimeterX (now HUMAN) at the door. On August 24, 2026, we sent sweetwater.com a plain request from a home connection and it loaded, HTTP 200, with PerimeterX signals in the page. Our request from a datacenter server, sent by a different client, was routed to a press-and-hold challenge. At the PerimeterX stores we re-tested in October, both addresses were refused (our PerimeterX guide), so this result shows what a plain client meets and leaves open how much the address weighed.
Sweetwater is one of the largest US music-gear retailers, the new-gear counterpart to the Reverb marketplace, and its pricing has a twist: it sells through sales engineers who often negotiate below the list price and bundle extras. The defense is PerimeterX, now HUMAN.
What proxies work best for Sweetwater?
US rotating residential proxies behind a real browser for reading, and a static ISP proxy for a logged-in account. Datacenter proxies draw the press-and-hold challenge on contact.
PerimeterX scored the datacenter IP down
PerimeterX (now HUMAN) works in layers (how to handle PerimeterX and HUMAN). A sensor script sets the _px cookies that later requests carry, and the server reads the TLS handshake before that; when the score tips, HUMAN serves the press-and-hold challenge. A client with no sensor data gets judged on the request alone. The same vendor guards Wayfair, Sam's Club and GNC, so the same setup applies: a residential exit that still needs a real browser that keeps its _px cookies.
The list price is a starting point
Sweetwater's pricing is worth a note because the page price is not always the transacted price. It sells through sales engineers who often negotiate a deal below the list price and bundle free extras or financing, so a dataset should record the list price while knowing the effective price can be lower for a negotiated order. That is a limit on what any scraper can see: the negotiated price lives in a conversation, not on the page. What the page reliably gives is the list price, stock, and specifications across a deep catalog.
Home connection
HTTP 200
the store loaded
Browsing allowed
normal session
Reputation passed
residential trusted
Datacenter server
Press-and-hold challenge
PerimeterX
_px cookies
no store
Reputation failed
hosting range distrusted
Which proxy type fits which job
| Sweetwater job | Proxy type | Why |
|---|---|---|
| List-price and stock monitoring | US rotating residential behind a browser | Datacenter draws the press-and-hold challenge |
| Specification and catalog collection | Rotating residential | Deep catalog, steady read |
| Review collection | Rotating residential | Separate endpoints, own limits |
| Account, cart | Static ISP | The session must keep one address |
| Cross-read with Reverb | Rotating residential | New-gear list price vs used marketplace spread |
| Parser tests against saved HTML | Residential (datacenter is challenged) | Datacenter is routed to the challenge |
Rotating residential IPs are the trusted addresses that load the site, and ISP proxies hold one address for an account. The two are compared in rotating vs static residential proxies.
Setup
Exit from US residential addresses behind a real browser, keep the _px cookies, and pace like a shopper (proxies for Playwright). Record the list price, stock and specifications, and note that the effective price can be lower for a negotiated order. For accounts, use a static ISP address. Pace like a shopper.
Sizing
Find how fast one residential IP reads behind a browser before PerimeterX challenges it, and add exits. A music-gear catalog is deep but not enormous, so this is usually a modest, steady read. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Accounts are one static ISP address each, and our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for Sweetwater
The test settles it: a datacenter client got the press-and-hold page on contact. Free proxies confirm a page loads from a clean residential IP, which our free proxy list and proxy checker cover. Reading Sweetwater needs paid residential, from $0.44/GB pay-as-you-go, behind a real browser. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not retry the challenge from the same datacenter address. Use a residential exit and a browser.
- Keep the _px cookies. They are the session's passport; discarding them resets the score.
- Record the list price as a starting point. The negotiated price is not on the page.
- Pace like a shopper. A steady flood from one IP is what PerimeterX catches.
- Watch the challenge rate. A rising share of press-and-hold pages means slow down or widen the pool. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy gives you a trusted residential address and keeps accounts apart. It does not pass the press-and-hold for you, and it does not reveal a negotiated price that lives in a conversation rather than on the page. Scraping sweetwater.com runs against its terms of use, a risk that stays with you regardless of the IPs. What a residential exit does is the one thing the datacenter IP could not in our test: load the site at all. Test with the free proxy list, then read list price and stock with residential from $0.44/GB, and pair it with Reverb for the used-gear side.
Sources
- HUMAN Security, HUMAN and PerimeterX merger: the vendor behind the challenge.
- Cloudflare, JA3/JA4 TLS fingerprinting: the handshake signal read before the sensor.
- HProxy test on August 24, 2026: identical plain GET to sweetwater.com from a residential IP (HTTP 200, store loaded) and a datacenter IP (routed to a PerimeterX press-and-hold challenge).
