Proxies for H&M meet Akamai at the door and a per-country price behind it. On 24 August 2026 we sent hm.com a plain request from a home connection and from a datacenter server, and both returned Akamai's Access Denied. The wall is Akamai, judged on the request from either address, so a real browser is required, and because H&M prices by country, the exit country decides which price you read.
H&M is a global fast-fashion retailer, part of a group that also runs COS, Arket, Weekday and & Other Stories, and its data is cross-country pricing plus collaboration drops that sell out. That makes the proxy job a geo-matched read behind Akamai, in the same family as Zara and Uniqlo.
What proxies work best for H&M?
Residential proxies exiting in the country you read, behind a real browser. A static ISP proxy for an account or a drop checkout. Datacenter proxies get Access Denied on contact.
Akamai judged the request
Both test requests got Access Denied from Akamai with no product. Akamai decided on the request, the TLS handshake (the JA3/JA4 signature read before any HTTP) and the header order a real browser sends with client hints (what is JA3/JA4 fingerprinting, how to scrape past Akamai). Past the door, Akamai's sensor and the _abck cookie keep scoring, with per-IP rate limits on top. The proxy gives the browser a residential address in the right country; the browser satisfies the sensor.
The price follows the country, the drop follows the calendar
H&M localizes hard. It runs a storefront per country in local currency with its own assortment and promotions, so the same item can be a different price in another market, and some pieces launch only in some countries. A dataset needs one row per country per item with the currency recorded, and geo-testing with proxies confirms the exit lands where you intend.
The drops are the second surface. H&M's designer collaborations sell out quickly online, so they behave like hyped releases: a per-item, time-sensitive read that wants clean residential exits and a browser that behaves, with a sticky session for a checkout. The apparel-drop discipline is the same as sneaker copping.
Exit country
sets storefront and currency
Akamai sensor
product data gated
Local assortment
some pieces country-only
Collaboration drops
sell out fast
Which proxy type fits which job
| H&M job | Proxy type | Why |
|---|---|---|
| Cross-country price comparison | Residential, one pool per country | Per-country storefronts and currency |
| Assortment and availability by market | Residential in that country | Some pieces launch only in some markets |
| Collaboration drop monitoring | Sticky residential per session | Time-sensitive, sells out fast |
| Review and catalog collection | Rotating residential | Separate endpoints, own limits |
| Account, cart, drop checkout | Static ISP | The session must keep one address |
| Parser tests against saved HTML | Datacenter or free | The live site denies bare clients |
Rotating residential IPs pass Akamai and land in the country you choose, and ISP proxies hold one address for an account or a drop. The two are compared in rotating vs static residential proxies.
Setup
Drive a real browser so the sensor sets _abck, and keep the cookies (proxies for Playwright). Run one residential pool per country you price, verify the exit country, and record the currency with every price. For a drop, hold one sticky exit from entry through checkout. Pace like a shopper.
Sizing
Country is the first multiplier: one pool per market. Within each, find how fast one residential IP reads behind a browser before Akamai challenges it, and add exits, with extra headroom around collaboration launches. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Our pricing is pay-as-you-go with a balance that does not expire.
Free versus paid for H&M
The test settles it: a datacenter client with no browser got Access Denied on both IPs. Free proxies confirm which country a page serves, which our free proxy list and proxy checker cover. Reading prices needs 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 Access Denied without a browser. Akamai will keep refusing; the fix is the sensor.
- Match the exit to the market. A mismatched exit reads the wrong currency and flags the session.
- Keep the sensor cookies. Discarding
_abckrestarts the sensor. - Hold one exit through a drop checkout. A rotation mid-checkout loses the session.
- Watch the challenge rate per country pool. A rising share means slow that pool. The full list is in avoiding IP bans while scraping.
What a proxy does not do here
A proxy lands a browser in the right country and keeps accounts apart. It does not run Akamai's sensor, and it does not equalize the per-country prices. Scraping hm.com runs against H&M's terms of use, a risk that stays with you regardless of the IPs. What a country-correct residential exit does is read the local price a datacenter client cannot reach. Confirm the destinations with the free proxy list, then price each market with residential from $0.44/GB.
Sources
- Akamai, Bot Manager: the vendor behind our Access Denied page.
- Cloudflare, JA3/JA4 TLS fingerprinting: fingerprinting before the first HTTP request.
- HProxy test on 24 August 2026: plain GET requests to hm.com from a residential connection and a datacenter server, both returning an Akamai Access Denied page.