United Airlines is a window, not just an airline. Its own network is one of the largest in the world, and as the anchor of Star Alliance it shows partner itineraries and award space across a web of carriers that no single-airline site of its size matches. That reach is why award-search tools and fare trackers read united.com so closely, and reading a window that wide, on a schedule, is where proxies for United Airlines come in: the site sits behind the same Akamai bot management as its US rivals, and at the volume the breadth invites, one address does not last.
We run a proxy network, and United traffic reaches us from fare trackers, award-search products and travel-data teams. This page covers what is specific to United: why the network breadth makes it worth reading, how Akamai guards the fare search, which proxy type fits and how to size it. The sector background is in travel fare aggregation, and the closest siblings are proxies for American Airlines and proxies for Delta.
What proxies are best for United Airlines?
Rotating residential proxies driven by a real browser, pinned to the market you are reading, with a static residential (ISP) exit for MileagePlus account work. United renders fares with JavaScript and runs Akamai Bot Manager, so a home connection and a real browser are both required, and a datacenter address is a 403 before the fare engine answers. Mobile sits above all of this, for the runs nothing else clears.
Breadth is the reason to read it
The case for reading United closely is not a pricing quirk, it is coverage. United operates one of the widest route maps in commercial aviation and sits at the center of Star Alliance, the largest of the airline alliances, so a single united.com search can surface United-operated flights and a broad set of partner itineraries, including award space on carriers a traveler could not easily search elsewhere. For an award-search product, that makes United one of the highest-value sources on the web: one site, many airlines' availability.
That value comes with volume. A wide network means more routes, more connecting itineraries per route, and more partner permutations per search, so a United tracker generates more reads per route than a point-to-point carrier does. More reads from one address is the fastest way to be recognized as automated, which is the problem a residential pool solves.
Why United is a high-value, high-volume read
- one of the largest
- Own network
- Star Alliance
- Alliance
- many
- Reads per search
global route map
partner itineraries and award space
interline permutations multiply
Source: United network and Star Alliance membership
How United blocks you
United.com sits behind Akamai Bot Manager, the same class of defense on American, Delta and Lufthansa. Akamai builds a trust score from the TLS handshake (the JA3/JA4 fingerprint taken from the ClientHello before any HTTP is sent), the JavaScript environment and behavioral telemetry, and it issues a 403 to a client whose handshake looks like a scripting library before the request reaches the fare engine (ScrapingBee, Python flight scraper). The fare results load with JavaScript into a near-empty shell, so a plain fetch returns no prices.
The rule that follows is the shared one: a residential address Akamai does not start by distrusting, plus a real browser whose handshake and behavior match a human. In published testing a datacenter proxy returned 403 with correct headers while the same request through residential cleared (RapidSeedbox, flight scraper guide).
Which proxy type fits: residential, datacenter, ISP, or mobile
Datacenter proxies fail the trust score first. Keep them for building a parser against saved responses.
Rotating residential proxies are home connections from a pool, one per search, rotated, pinned to the market, and they carry the trust score that clears Akamai when paired with a real browser (background in what is a residential proxy). The breadth of United's results makes a wide pool matter more here than on a small carrier.
ISP proxies are static residential addresses for MileagePlus sessions.
Mobile proxies are carrier IPs shared by many handsets, kept for the runs that keep drawing 403s.
| United job | Proxy type | Why |
|---|---|---|
| Fare and award tracking across the network | Rotating residential + real browser | Akamai trust score, JS render, wide pool for the volume |
| Reading United fares on metasearch | Per that site's guide | Inherit the channel's defenses |
| MileagePlus account actions | ISP (static residential) | Session and account on one address |
| Runs that keep getting 403s | Mobile | Carrier ranges carry high trust |
| Parser development | Datacenter or free list | Saved pages, nothing at stake |
Free versus paid for United Airlines
A free proxy is a shared datacenter address, the profile Akamai rejects first, and it will not survive the fare search, still less the volume United's breadth invites. For a quick look from another country, a free proxy sometimes serves, and our free proxy list and proxy checker are free. For a tracker, paid residential behind a real browser is the floor; ours starts at $0.44/GB pay-as-you-go with no KYC.
Setting it up
Drive a real browser behind a residential exit (Playwright, Puppeteer), build searches directly, and wait for the results to render. Rotate one IP per search for public fares and hold a sticky ISP exit for MileagePlus work; the split is in rotating vs static residential proxies. Because a single United search can return many partner itineraries, parse defensively: the shape of the results changes with alliance availability, and a rigid parser breaks on the wide days.
How many IPs, and how fast
Sizing (rotating residential, one refresh cycle):
searches/cycle = routes x dates
= 500 routes x 60 dates = 30,000 searches
per search = a browser render behind Akamai; itineraries multiply
per address = a few searches, then rotate
Refresh near-term dates daily, far dates weekly. The pool spreads it.
Our pricing is per gigabyte with no expiry, so the wide-network volume is billed as the bandwidth it actually uses.
Staying unblocked on United
- Residential IP plus a real browser. Akamai scores both.
- Guard the handshake. The TLS fingerprint is the top vector.
- One search per address, then rotate. The breadth means more reads, so spread them wider.
- Parse for variety. Interline results change shape; do not hard-code one layout.
- Back off on the first 403. The checklist is in avoiding IP bans while scraping.
The limits worth knowing
Proxies give a United read a trusted address and spread a wide-network tracker across enough of them that united.com sees travelers. They do not clear Akamai alone, and they do not change United's terms of service. Drive a real browser, match the market, and size from searches, remembering that United's interline breadth multiplies the reads.
Testing and manual checks stay free on our free proxy list and proxy checker. For a fare tracker, rotating residential at $0.44/GB pay-as-you-go behind a real browser is what reads United.
Sources
- ScrapingBee, how to build a Python flight scraper, on Akamai Bot Manager, JA3/JA4 and the JavaScript shell.
- RapidSeedbox, flight scraper guide, on datacenter 403s clearing through residential exits.