Proxies for Pizza Hut: 20,000 Units, Local Coupons, and an Akamai Block

Pizza Hut is Domino's rival with a harder front door and a bigger footprint. The Pizza Hut Division runs 19,974 units, 68 percent of them outside the US, and more than 99 percent are franchised, all under Yum Brands, which in 2025 began a strategic review of the brand (Yum Brands, FY2025 reporting). Franchisees set their own prices and their own local coupons, so the same order has thousands of prices, and each country runs its own site. That is the same store-level, per-country structure that makes Domino's a dataset rather than a menu, but where Domino's opened its door to our request, Pizza Hut refused it.

On 24 August 2026 pizzahut.com answered our datacenter server with an Akamai-fronted 403, and the free proxies that connected were refused too. A block is not a challenge; the fix is a residential address, not a browser trick. The door, the jobs, and the setup that follows are below.

The short answer

Residential proxies in the country whose site you read, pinned to the metro for US store-level work, driving a real browser, one session per store. A static ISP proxy per account for any login. Datacenter and free exits are refused at the door; the count is below.

Pizza Hut as a target

Store menus and prices, built around a chosen store, set by franchisees and varying by market. Local coupons, per store, which change often. The other country sites, each its own property in its own currency, 68 percent of the estate. The marketplace delivery menus, each per store. The store locator, across nearly 20,000 units. And Hut Rewards, the app and loyalty layer, which is not a data job.

Once a residential address is past the block, the store menu and coupons load around a chosen store from Pizza Hut's own API calls.

Jobs a proxy is right for

• Store-level price monitoring. The same order across a metro, on a schedule, for franchise consultants, competitors and price-intelligence firms.
• Local coupon tracking. Which coupons each store runs and how they differ across a city, the shape of the Domino's coupon job.
• Cross-country comparison. Pizza Hut priced across markets in local currency, read from an exit in each country, the method in geo-testing with proxies.
• Delivery-price monitoring. Pizza Hut's delivery prices per store on the marketplaces.
• Location data. The store list per country, for site selection and competitor mapping.

Jobs a proxy is not for

Hut Rewards and account-gated coupons. They attach to a phone or email and the app on a device; farming coupons runs against Pizza Hut's terms.

Ordering. A real store and payment method, not a network property.

The door: an Akamai block

On 24 August 2026 the direct request from our German server returned an empty HTTP 403 through Akamai. Of twenty elite HTTP proxies from our free proxy list, one call apiece, 18 never connected and the two that did were refused the same way; the site never loaded. The rule evidently matches datacenter address space, and possibly non-US space; we did not test a US datacenter exit, so treat that as open. A block wants an address it is written not to match, which for a US pizza chain is a US residential address. Scraping past Akamai covers the layer the refusal came through, and the difference between a block and a challenge is in scraping past Cloudflare.

Type by job

For the general split, datacenter vs residential proxies.

Free proxies here

Zero of twenty, and structurally so: free proxies are datacenter addresses and the rule blocks datacenter addresses. There is no manual-look case to describe. For the sweep, our residential proxies start at $0.44/GB, pay as you go, no KYC, in the countries and metros you need.

Setup

1. Residential exit that matches the market, metro-pinned for US. This is the difference between a page and a refusal. A Chicago store from a Chicago exit; a UK Pizza Hut from a UK exit. Launch flags are in the Puppeteer proxy guide.
2. One session per store, coupons diffed weekly. Coupons rotate on a cycle; read each store once per cycle and diff. Sticky vs rotating proxy sessions covers the two modes.
3. Measure each country's door. The US is a block; other markets may differ. Read the door before the sweep.
4. Retire an exit on the first refusal. Avoiding IP bans while scraping has the rest.

Sizing

US store price and coupon index, 250 stores, weekly:
  store sessions per sweep     250
  pages per session            3-4 (menu, coupons)
  sessions per exit per day    4-6
  exits in rotation            ~20-25 US residential, metro-pinned

Bandwidth is the meter, and menu and coupon pages with images blocked are small. Our pricing has no subscription and no expiring balance.

Where it stops

A residential address that matches the market is what turns the refusal into a page, and it is all the proxy contributes. Hut Rewards, ordering and Pizza Hut's terms, which prohibit scraping, stay where they were. Past that, a market-matched residential exit with a real browser reads public store prices and coupons the way customers in each place see them: one store per session, human pacing, refusal rate logged.

The rival with an open door and the same store-and-coupon structure is in proxies for Domino's; the Yum sibling where test markets make city-level reads the point is in proxies for Taco Bell.

Sources

• Yum Brands, FY2025 reporting (Pizza Hut Division 19,974 units, 68 percent outside the US, more than 99 percent franchised; 2025 strategic review of the Pizza Hut brand): sec.gov
• HProxy measurement, 24 August 2026: one direct request to pizzahut.com from a datacenter server (empty HTTP 403 through Akamai) and 20 elite HTTP proxies from our free proxy list (18 no connection, 2 refused, 0 site).