Proxies for Adorama meet DataDome at the door, and DataDome was unusually candid about it. On 24 August 2026 we sent adorama.com a plain request from a home connection and from a datacenter server, and both returned HTTP 403 with a datadome cookie, x-datadome headers, and an x-datadome-riskscore header that exposed the scoring itself. The address did not matter; DataDome judged the client on the request and refused it from either IP, so a real browser is required from the start.
Adorama is one of the two large New York pro-photo and video retailers, the natural comparison to B&H Photo, and its data is worth reading for pro-gear prices, a deep used department, and MAP-restricted items. The difference from B&H is the door: Adorama runs DataDome where B&H layers Cloudflare and F5 Shape, so a cross-retailer photo project needs both setups.
What proxies work best for Adorama?
US rotating residential proxies behind a real browser that solves the DataDome challenge. A static ISP proxy for a logged-in account. Datacenter proxies get the 403 on contact.
DataDome judged the request, and showed its work
DataDome scores every request on device fingerprinting, the TLS handshake and header order, and serves a 403 with a JavaScript challenge to anything automated, usually on the first request; solving it in a real browser earns the datadome cookie that grants access for a period (how to get around DataDome). The x-datadome-riskscore header in our response is DataDome's own risk assessment made visible, a useful confirmation that the block is a score, not a fixed rule. The setup order is browser first, then residential exit, then region matching, and the browser has to actually solve the challenge. AutoZone and Anthropologie run the same vendor, so a DataDome-aware pipeline transfers (proxies for AutoZone).
The price is not the sticker
Two pricing wrinkles make a complete read more than one number. Adorama sells new and used gear, with a large used department at condition-graded prices, so a model has a new price and one or more used prices. And some manufacturer-restricted items hide the price until the item is in the cart, a common pro-gear pattern, so a scraper has to run the add-to-cart step to reveal it. Capture new, used and cart-revealed prices separately, the same way the B&H read works.
Request
DataDome scores it
403 + challenge
riskscore header exposed
Browser solves it
datadome cookie issued
New, used, cart-revealed
capture each
Which proxy type fits which job
| Adorama job | Proxy type | Why |
|---|---|---|
| Pro-gear price monitoring | US rotating residential behind a browser | DataDome challenges the request |
| New-vs-used price capture | Rotating residential | Two price regimes per model |
| Cart-revealed (MAP) price capture | Sticky residential per session | Requires an add-to-cart flow |
| Cross-retailer photo comparison | Rotating residential | Adorama plus B&H, different doors |
| Account, cart | Static ISP | The session must keep one address past DataDome |
| Parser tests against saved HTML | Datacenter or free | The live site refuses bare clients |
Rotating residential IPs let a browser session survive DataDome's scoring, and ISP proxies hold one address for an account or a cart flow. The two are compared in rotating vs static residential proxies.
Setup
Lead with a real browser so DataDome's challenge has a client to run against, and keep the datadome cookie (proxies for Playwright). Capture new and used prices separately, run the add-to-cart step for MAP items, and hold one exit per session. Pace like a shopper.
Sizing
Size by request rate: find how many pages one residential session sustains before DataDome re-challenges, and add exits. The cart-reveal flow costs more requests and bandwidth per item, so budget for it (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 Adorama
The test settles it: a datacenter client with no browser got the 403 on both IPs. Free proxies confirm the pipeline forwards traffic and an address is alive, which our free proxy list and proxy checker cover. Reading Adorama needs paid residential, from $0.44/GB pay-as-you-go with no KYC, behind a browser that satisfies DataDome. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not retry the 403 without a browser. DataDome will keep refusing; the fix is the challenge.
- Keep the datadome cookie. It is the session's pass; discarding it forces a fresh challenge.
- Capture new, used and cart-revealed prices separately. One blended number is wrong.
- Pace like a shopper. A steady flood from one IP is what DataDome catches.
- Watch the 403 rate. A rising share 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 a browser a clean address and keeps accounts apart. It does not solve DataDome's challenge, and it does not reveal a MAP price without the cart step. Scraping adorama.com runs against its terms of use, a risk that stays with you regardless of the IPs. What a residential exit does is let a browser that has cleared DataDome read new, used and cart-revealed prices, and it pairs with the B&H setup for a full pro-photo comparison. Test with the free proxy list, then monitor with residential from $0.44/GB.
Sources
- DataDome, bot protection: the vendor behind our 403 and the risk-score header.
- Cloudflare, JA3/JA4 TLS fingerprinting: the handshake signal DataDome scores.
- HProxy test on 24 August 2026: plain GET requests to adorama.com from a residential connection and a datacenter server, both returning HTTP 403 with a
datadomecookie and anx-datadome-riskscoreheader.