Proxies for Zara answer a question with an unusually large price attached: what does this exact item cost in another country? The answer is not a rounding difference. An RBC analysis of 40 Zara garments found prices at least 60 percent higher in the US and Mexico than in Spain, with the United States about 92 percent higher and South Korea about 96 percent (FashionUnited, where Zara's prices double). The same dress, nearly double the price, decided by which country you are shopping from. Zara's parent Inditex operates in 214 markets (Inditex, FY2025 results), each with its own currency and price list, which makes cross-country price intelligence the main reason anyone scrapes Zara, and the exit country the main thing a proxy provides.
Getting the price out is the hard part, and we watched Zara defend it on 24 August 2026. A request to zara.com from a home connection returned a small HTML shell, not the store: an Akamai interstitial carrying a bm-verify token and a script that computes a proof-of-work answer and posts it to /_sec/verify?provider=interstitial before reloading the page. The same request from a datacenter server returned a Service Unavailable page outright.
What proxies work best for Zara?
Residential proxies exiting in each country whose prices you read, behind a real browser that can run Akamai's proof-of-work. A static ISP proxy for a logged-in account. Datacenter proxies get Service Unavailable.
Zara is 214 price lists wearing one brand
Inditex prices Zara market by market. The RBC figures are the headline, but the structure underneath is the point: 214 markets, each with a storefront, a currency and a price list that reflects local costs, duties, positioning and what the market will bear. Inditex's online sales reached 10.7 billion euros in FY2025, so these are heavily-trafficked storefronts, not afterthoughts (Inditex, FY2025 results).
Three consequences for a data project.
- Each country needs its own exit. There is no global Zara price to read; there are per-country prices, and each one comes from an IP in that country. This is the whole job, and geo-testing with proxies is how you confirm an exit lands where you think.
- Currency and availability travel with the country. A dataset needs the currency and the market on every row, and stock differs by market because collections roll out unevenly.
- Fast fashion adds time pressure. Zara drops new collections continuously and restocks unpredictably, so monitoring is not a monthly snapshot but a running watch, with bursts around releases.
The audience is resellers arbitraging price gaps across borders, competitors and analysts tracking a bellwether of fast-fashion pricing, and shoppers checking whether an item is cheaper one market over. All of them need the same thing: the real local price, read locally.
Akamai's proof-of-work, caught in the act
The interstitial we captured is worth reading closely, because it shows exactly what a scraper is up against. Instead of the catalog, zara.com returned a page that loads an Akamai challenge frame and runs a script computing a value (in our capture, a sum of two numbers used as a proof-of-work "pow") which it posts with the bm-verify token to /_sec/verify. Only when that answer validates does the real page load. This is Akamai's interstitial challenge: it forces the client to prove it stores cookies and executes JavaScript, and it applies a time penalty to anything that cannot (how to scrape past Akamai).
Plain request
home IP, browser user-agent
Interstitial shell
bm-verify token, akam challenge frame
Proof-of-work script
compute answer, POST to /_sec/verify
Real page
only after the answer validates
Two things follow for proxy choice. A bare HTTP client cannot run the proof-of-work, so it never reaches a price, which is why the browser is mandatory. And the datacenter address did not even get the challenge, it got Service Unavailable, so the reputation gate rejects datacenter ranges before the puzzle is offered. Only a residential IP behind a real browser gets to run the challenge and continue. Underneath, Akamai keeps its usual sensor-and-_abck scoring going (how the _abck cookie works), and reads the JA3/JA4 fingerprint before any of it (what is JA3/JA4 fingerprinting).
Which proxy type fits which job
| Zara job | Proxy type | Why |
|---|---|---|
| Cross-country price comparison | Residential, one pool per country | The exit country is the price; each market differs |
| New-collection and restock monitoring | Residential in that country, sticky per session | Fast-fashion drops need frequent, shopper-paced reads |
| Review and catalog collection | Rotating residential | Separate endpoints, own limits |
| Logged-in account, wishlist, cart | Static ISP | The session must hold one address past the challenge |
| Currency-and-availability audits | Residential per market | Currency and stock travel with the country |
| Pipeline and liveness tests | Datacenter or free | Service Unavailable on contact; only proves plumbing |
Rotating residential IPs are real home connections in the country you pick, which pass the reputation gate and let the browser run the challenge. ISP proxies never change, which a logged-in account needs. The two are compared in rotating vs static residential proxies, and the fast-fashion neighbors are covered in proxies for SHEIN and proxies for ASOS.
Setup
Run a real browser and let it solve the interstitial. Playwright or Puppeteer behind the proxy so Akamai's proof-of-work script executes and posts its answer, and keep the resulting cookies for the session (proxies for Playwright, proxies for Puppeteer). A bare client is stuck at the shell.
Run one pool per country. Read zara.com/es from a Spanish exit, zara.com/us from a US exit, and so on, and record the market and currency on every price. Verify the exit country before trusting the data; a mislocated exit produces a price no local shopper sees and a reputation flag at the same time.
Keep one exit per session and pace like a shopper. A sticky window per session so the challenge cookies stay valid, human timing inside it, and rotation between sessions rather than within one (sticky vs rotating proxy sessions).
Sizing
Country is the first multiplier: one pool per market you price. Within a pool, find how fast one residential IP can read behind a browser before Akamai re-challenges, and add exits to scale. Add headroom around drops, when new collections and restocks pull watchers to the same pages. Budget browser-level bandwidth for an image-heavy fashion catalog, well above bare HTML (headless browser proxy bandwidth cost). Accounts are one static ISP address each, and our pricing is pay-as-you-go with a balance that never expires, so pricing twenty markets in a burst and one in a quiet week costs only what each uses.
Free versus paid for Zara
A datacenter IP got Service Unavailable, and a home IP still faced a proof-of-work; a free proxy is the former with none of the browser the latter needs. Free proxies can show which country a Zara domain serves and confirm an address is alive, which our free proxy list and proxy checker do. Reading Zara's prices takes paid residential in each country, from $0.44/GB pay-as-you-go with no KYC, behind a real browser. The line is in datacenter vs residential proxies.
Staying unblocked
- Do not retry the interstitial from a bare client. Without a browser it will never validate; the fix is running the proof-of-work, not resending.
- Keep the challenge cookies. They are what let the real page load; discard them and every request restarts at the shell.
- One exit per country per session. Reading France from a Spanish exit is wrong data and a flag.
- Pace like a shopper, especially on drop pages. One IP hammering a new-collection page is the pattern the sensor catches.
- Log challenges per country pool. Each market's pool is scored separately; a rising challenge rate in one is the signal to slow that pool. The general list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy lands you in the right country and keeps sessions apart. It does not compute Akamai's proof-of-work, does not make a bare client into a browser, and does not equalize the per-country prices, which are Inditex's decision, not an artifact you can route around. Scraping Zara's sites runs against Inditex's terms of use, a risk that stays with you regardless of the addresses.
What a country-correct residential exit does is get a real browser to the point where it can solve the challenge and read the local price, which, given gaps of 90 percent between markets, is a number worth reading correctly. Confirm the destinations with the free proxy list, then price each market through residential from $0.44/GB, one pool per country, and record the currency with every row.
Sources
- FashionUnited, South Korea, US and China: where Zara's prices double: the RBC analysis of 40 garments, US about 92 percent and South Korea about 96 percent higher than Spain.
- Inditex, FY2025 results: 214 markets and 10.7 billion euros of online sales.
- Akamai, Bot Manager: the vendor whose interstitial challenge we captured.
- Cloudflare, JA3/JA4 TLS fingerprinting: the handshake signal read before the challenge.
- HProxy test on 24 August 2026: zara.com/us returned an Akamai interstitial (a
bm-verifytoken and a proof-of-work script posting to/_sec/verify?provider=interstitial) to a residential IP, and a Service Unavailable page to a datacenter IP.