Proxies for Dillard's meet Akamai at the door and a fast-moving clearance rack behind it. On 24 August 2026 we sent dillards.com a plain request from a home connection and from a datacenter server, and both returned an Akamai "Access Denied" response (served from Akamai's network, refusing the client). The wall is Akamai, judged on the request from either address, so the setup starts with a real browser rather than a clean IP alone.
Dillard's is a US department store, and the reason it draws scrapers is specific: its clearance engine. Dillard's marks merchandise down in stages and then to deep final prices, the best deals sell out quickly, and the markdowns vary by store, so deal hunters and resellers monitor it closely. That makes the proxy job a per-item, time-sensitive read against an Akamai-defended, store-priced site.
What proxies work best for Dillard's?
US rotating residential proxies behind a real browser, region-matched to the stores you read. A static ISP proxy for a logged-in account. Datacenter proxies get Access Denied on contact.
Akamai judged the request
Both test requests got the Access Denied treatment with no product behind it. Akamai decided on the request itself, 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). Past the door, Akamai Bot Manager keeps scoring through its sensor and the _abck cookie, with per-IP rate limits on top (how to scrape past Akamai). The proxy gives the browser a US residential address and spreads the rate; the browser satisfies the sensor. This is the same door the other department stores run, so a pipeline built for Macy's or Kohl's transfers here.
The clearance is the data, and it moves
Dillard's staged markdowns are the signal. An item drops in steps and then to a deep final price, the deep prices clear quickly, and because clearance is local, the same item can be a bargain at one store and untouched at another. For a monitoring project this means the unit of work is a store-item pair read on a schedule tight enough to catch a markdown before it sells through, and the reads have to spread across many residential exits so no single address looks like a monitor camped on the clearance section. It is the markdown-hunting version of the restock discipline in proxies for price monitoring.
Full price
the starting number
Staged markdowns
in steps, per store
Deep final price
clears fast
Sold out
before the next scrape if you are slow
Which proxy type fits which job
| Dillard's job | Proxy type | Why |
|---|---|---|
| Clearance and markdown monitoring | US rotating residential, region-matched, behind a browser | Akamai refuses datacenter; clearance is local and fast |
| Full-catalog price and stock | Rotating residential | Volume across a pool |
| Store-level stock, region by region | Sticky residential per store | Availability keys to the store |
| Brand and category collection | Rotating residential | Separate endpoints, own limits |
| Account, cart | Static ISP | The session must keep one address |
| Parser tests against saved HTML | Datacenter or free | The live site refuses bare clients |
Rotating residential IPs pass Akamai's reputation check and match a store's region, and ISP proxies hold one address for an account. The difference is in rotating vs static residential proxies.
Setup
Drive a real browser so the sensor sets _abck, and keep the cookies (proxies for Playwright). Read clearance on a tight schedule, pin the store, match the exit to its region, and record the store and the markdown stage with every price. Spread the polling across exits and jitter the interval so no single address hammers the clearance section. Pace like a shopper.
Sizing
Clearance monitoring is item-count times polling frequency, which is high if you track deep, so size from request rate: find how fast one residential IP reads behind a browser before Akamai challenges it, and add exits. Budget browser-level bandwidth (headless browser proxy bandwidth cost). Our pricing is pay-as-you-go with a balance that does not expire, which suits a markdown watch that spikes and quiets.
Free versus paid for Dillard's
The test settles it: a datacenter client with no browser got Access Denied 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 Dillard's needs paid residential, 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.
- Spread clearance polling. One address on the clearance section is the clearest monitor signal.
- Keep the sensor cookies. Discarding
_abckrestarts the sensor. - Pin the store and match the exit. A blended-store clearance price is a wrong number.
- Watch the challenge rate. A rising Access Denied 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 region-correct residential address and keeps accounts apart. It does not run Akamai's sensor, does not set the store, and does not make a clearance item restock. Scraping dillards.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 real browser look like a local shopper so Akamai admits it and the clearance reads for the store you mean. Test with the free proxy list, then monitor clearance with residential from $0.44/GB.
Sources
- Akamai, Bot Manager: the vendor behind our Access Denied response.
- Cloudflare, JA3/JA4 TLS fingerprinting: fingerprinting before the first HTTP request.
- HProxy test on 24 August 2026: plain GET requests to dillards.com from a residential connection and a datacenter server, both returning an Akamai Access Denied response.