Hotels.com is Expedia Group's hotel-only brand, and it fails a free proxy for the same reasons Expedia does, plus a loyalty layer of its own. We run a free proxy list and a verification engine, so we measured it: 120 fresh free proxies, one Hotels.com search page each. None returned real content. This is the measured version; the paid setup is in proxies for Hotels.com.
We pointed 120 free proxies at Hotels.com
On 24 August 2026, as part of a wider travel-site test, we took 120 HTTP proxies from our own free proxy list, each verified alive minutes earlier, and asked every one for a Hotels.com search page.
None returned real content. Seventeen were stopped by a bot challenge, and the other one hundred and three could not complete the request at all.
120 free proxies asked for one Hotels.com page
- 0
- Returned a real page
- 17
- Bot challenge
- 103
- Failed to connect
of 120
Source: HProxy, 120 HTTP proxies from our own free list, measured 2026-08-24
Why free proxies fail on Hotels.com
The result is the Expedia Group result: most proxies die, the rest are challenged. One hundred and three of 120 never connected, and the seventeen that did were met by the same bot management that guards Expedia, because Hotels.com runs on the same platform and prices by point of sale. The detail is in proxies for Hotels.com.
The member layer adds a second reason. Hotels.com shows a member rate tied to the One Key program in most markets, with the United Kingdom reverting to Hotels.com Rewards, and either way it appears only to a signed-in member on a stable address. A short-lived shared free proxy cannot hold that session, so the member rate is out of reach whatever the loyalty program is called.
The free pool behind the result
The failures are the pool, not the draw. Our free proxy data study, from 129M checks across 590K tracked proxies, finds the working free pool overwhelmingly on cloud networks, a few thousand alive at any moment, churning constantly, the wrong reputation and lifespan for a defended Expedia Group site.
What free proxies are genuinely good for here
Throwaway, website-only checks where failure costs nothing: whether a Hotels.com page loads from another country, or a parser test against a saved page. Run any candidate through our free proxy checker first, and read are free proxies safe before routing real traffic.
Free versus paid for Hotels.com
| What you are trying to do | Free proxy | Paid residential |
|---|---|---|
| Open a public rate from another country | Sometimes, briefly | Reliably |
| Return real listings on a schedule | No, 0 of 120 in our test | Yes |
| Read a One Key member rate | No, cannot hold a session | Yes, static ISP exit |
| Read the market's point-of-sale price | No, wrong IP profile | Yes, in-market residential |
| Cost | $0 plus your time | From $0.44/GB, pay as you go |
When the job outgrows free
The moment you need Hotels.com rates that come back, or the member rate, you need a residential address the platform trusts and a static ISP exit that can hold a member session. Ours are $0.44/GB, pay as you go and no KYC, so trying them costs cents rather than a subscription. The setup is in proxies for Hotels.com, and the wider picture is in free proxies versus travel sites. Keep our free proxy list for the throwaway checks and nothing that has to return.
Sources
- HProxy travel-site test, measured 24 August 2026: 120 HTTP proxies from our own free proxy list, one Hotels.com page each, 0 returning real content, 17 challenged, 103 failing to connect. Method in free proxies versus travel sites.
- HProxy, free proxy data study, for pool size, composition and lifetimes.
- HProxy, proxies for Hotels.com, on the member layer and Expedia Group backend.