UK residential proxies: regions, cities and sessions

UK residential proxies route requests through home broadband connections in the United Kingdom, so the target sees an address that a British consumer ISP such as BT, Sky, Virgin Media or TalkTalk assigned to a household, on a network that IP databases classify as residential. With region and city targeting, the exit can sit in the part of the UK whose delivery options, search results or ads the job needs.

A stock check returns “available for delivery” from a London exit, while the same product cannot ship to a Belfast or Inverness postcode. A rank tracker reads Manchester results for a page that targets Glasgow. A test script fails because it asserted the country code “UK” and the lookup answered “GB”. Each of these jobs had a UK exit. Each still got the wrong answer.

What UK residential proxies are

Residential. A UK residential proxy exits through a device on a home broadband line. The address belongs to an autonomous system (ASN) that a consumer ISP operates, so IP intelligence databases classify it as residential, not hosting. The residential proxy explainer covers how that classification works and how residential exits are sourced.

UK. That address geolocates to the United Kingdom in the databases that sites use, and in most cases to a constituent nation, a region and a city as well. The label is an estimate built from registry data, ISP feeds and measurement, and MaxMind’s accuracy notes (checked October 2026) put country accuracy at 99.8% worldwide, with precision falling at each finer level.

Gateway. A customer never connects to the home device directly. Requests go to a provider gateway over HTTP or SOCKS5 with a username and password, and the gateway picks a UK exit that matches the order’s location and rotation settings.

GB vs UK country codes in tools

The ISO 3166-1 code for the United Kingdom is GB. UK is only “exceptionally reserved”, at the request of the UK’s standards body, because the country’s internet domain was registered as .uk. Geolocation APIs, ad platforms and most proxy dashboards therefore answer GB, and a config, test or database filter that expects “UK” silently matches nothing. Some location lists also spell the country as England, which covers one nation of four. Match on GB, and treat “United Kingdom”, “UK” and “England” as labels to normalise.

Why the UK location matters

For most national pages, a country-level exit is enough. Some things a site shows depend on where in the UK the visitor sits, and one thing a US guide would expect, tax, mostly does not.

Prices already include VAT. Prices shown to UK consumers must include VAT and other taxes, under the Price Marking Order 2004 (gov.uk guidance, updated September 2025). A shelf price from London and one from Leeds normally match, so region targeting buys little for a plain price check.

Delivery and stock differ. Delivery is where UK geography shows up. The Advertising Standards Authority’s guidance on delivery charges expects “UK delivery” to cover Northern Ireland and the Scottish islands, because surcharges and exclusions there are a recurring complaint. Some retail sites also estimate the nearest store and delivery window from the IP until the visitor enters a postcode.

Devolved rules change the page. England, Scotland, Wales and Northern Ireland set some rules separately. Scotland, for example, sets a minimum unit price for alcohol (gov.scot, raised on 30 September 2024), so a drinks retailer’s Scottish shelf can differ from its English one.

Local search and ads. A query with local intent returns map results for the area around the searcher, and campaigns are targeted by region and city. Read Glasgow rankings from a London exit and the tracker records London.

Age checks. Since 25 July 2025, Ofcom has enforced the Online Safety Act’s requirement for highly effective age checks on services that host content harmful to children. A UK exit sees the age gate a UK visitor sees, so a localization QA run should record the gate as part of the page under test.

UK targeting levels explained

Every order for UK residential proxies picks a level. The finer the level, the smaller the set of online devices that can serve it, and the less certain the label the target reads.

On proxymint, rotating residential orders take a country, a region and a city. Only places with devices online at the moment of ordering appear in the list, and the location can be changed later on a live package. For postcode pages, the reliable route is a city exit plus the site’s own postcode or store picker, which is where the site keeps that setting anyway.

How accurate UK city labels are

City is where geolocation gets soft. Consumer ISPs route traffic through regional hubs, so a household in a commuter town can be labelled with the nearest large city, and two databases can name different cities for the same address. MaxMind publishes per-country figures in its accuracy comparison for anyone who needs the UK number.

Pick city only when the page changes by city. Fewer households are online at any moment in a smaller city, so per-request rotation there repeats addresses sooner, and the request rate has to stay at what the target allows. If the city is not in the list, or the job needs more distinct addresses than one city returns, widen the order to the region, then to the country.

Rotating or sticky UK sessions

Rotation decides how long one UK exit serves the job. proxymint’s residential orders offer three settings, chosen on the order and changeable later with the same logins: a new IP on every request, a timer from 5 to 60 minutes, or sticky for as long as the device stays online. The rotating vs sticky proxies guide covers the trade in depth.

Every request. Fits stateless collection: product pages, search results, catalog checks across the UK. Each request leaves from a different household, which spreads load across many addresses.

Timed, 5 to 60 minutes. Fits short flows that carry a cookie: a postcode checker, a basket, a few pages of a session. Pick a window longer than the flow.

Sticky. Fits a browser session that has to keep one address until it ends. Home routers restart and devices go offline, so a sticky residential session lasts as long as that device stays online.

When one UK identity has to hold for weeks, such as a seller dashboard or a partner’s firewall rule, that is the job of static ISP proxies: one United Kingdom address assigned to the order for the whole term. The ISP vs rotating residential comparison walks through that split.

UK use cases that fit

UK residential proxies serve jobs where the page differs for home users in Britain, or where a hosting address gets a different answer.

• Price and stock monitoring across UK retailers, including delivery options and availability by city.
• Local search tracking by city, where the engine permits automated access.
• Ad verification on desktop and home networks, checking that a campaign runs in the regions and cities it was bought for.
• Property and listings research on UK portals, reading public listings as a home visitor in each area sees them, within each portal’s terms.
• Brand protection and marketplace monitoring, finding counterfeit or unauthorised listings as a UK shopper sees them.
• Localization QA, confirming a UK launch shows pounds sterling, VAT-inclusive prices, UK delivery terms and the right age and cookie notices.

Legal and responsible use

Using a proxy is lawful in the UK; what matters is the job. Public pages only, the target’s terms first, and a block or a challenge means the job slows down or stops. Collecting personal data brings UK GDPR into play, so the collection needs a lawful basis, and the Information Commissioner’s Office applied that test to web scraping in its December 2024 generative AI consultation outcomes. Age checks under the Online Safety Act are a legal duty on the site, and no proxy job should try to get past one.

Checking a UK exit first

Before a job on UK residential proxies runs, confirm the exit is where the order says. Three requests settle it.

# 1. exit IP, network (ASN) and location as one database sees it
curl -s -x http://USERNAME:PASSWORD@HOST:PORT https://ipinfo.io/json

# 2. the same exit in a second database (put the IP from step 1 in place of EXIT_IP)
curl -s https://ipapi.co/EXIT_IP/json/

# 3. which resolver looks up names for this exit
curl -sL -x socks5h://USERNAME:PASSWORD@HOST:PORT https://edns.ip-api.com/json

Read the output this way:

• Country should be GB in both lookups, not UK.
• Network should name a consumer ISP, not a hosting company or cloud provider.
• Region and city should match the order. If the two databases disagree on city, the target may disagree too, and only the target’s own lookup decides.
• Resolver should be on the proxy side, not the client’s own ISP or office network.
• Reputation is read with care. A home broadband address on Spamhaus’s Policy Block List (PBL) is normal: ISPs list consumer ranges there because they should not send mail directly, and Spamhaus says a PBL listing carries no judgement of abuse. Only the spam and exploit lists (SBL, XBL) describe how an address behaved.

Run this for a few dozen exits, not one, to see how many distinct addresses a city returns and how often the two databases agree. The proxymint Lab #1 page shows a similar check run against a US exit, with the commands and how to read the resolver result.

Keeping the session consistent with the exit

The exit IP is one location signal. Sites also read the browser’s time zone, language and DNS path, and a UK exit with a New York clock is a mismatch any detection script can score. The guide to how websites detect proxies covers these checks in detail.

Time zone. Great Britain and Northern Ireland share one zone, Europe/London. It runs on GMT in winter and on British Summer Time from the last Sunday in March to the last Sunday in October, per gov.uk (checked October 2026). A script with a fixed +00:00 offset is an hour wrong for seven months of the year.

Locale. Set en-GB, not en-US, so navigator.language, the Accept-Language header and date formats match a British visitor.

DNS. Use an http:// proxy URL or socks5h:// so names resolve on the proxy side. With plain socks5:// many clients resolve locally, and a CDN can answer for the client’s location instead of the exit’s.

In Playwright, each browser context carries its own proxy, locale and time zone:

const context = await browser.newContext({
  proxy: { server: 'http://HOST:PORT', username: 'USERNAME', password: 'PASSWORD' },
  locale: 'en-GB',
  timezoneId: 'Europe/London',
});

Start each city or region in a fresh context, so cookies and a saved postcode from one market do not follow the job into the next.

Residential vs other UK proxy types

Every proxy category has UK jobs it fits. Pick by requirement.

Rotating residential proxies cover the broad consumer-origin work: many UK addresses, chosen by region and city, rotated per request or held for a session. Mobile proxies fit apps and platforms that expect a carrier origin, with country, region and city targeting as well. Datacenter proxies handle volume on UK targets that accept hosting networks, such as APIs and uptime checks.

A UK VPN is a different tool. It tunnels a whole device through a few shared servers, usually on ranges that sites already know as VPN space, while a proxy is set per application or per browser context and can rotate or hold its exit per order. For collection, ad checks and QA run from code, the proxy is the one built for the job.

Choosing UK residential proxies

Start from the page. If it is the same across Britain, a country-level GB exit is enough and keeps the widest pool. If delivery, devolved rules or regional promotions change it, target the region. Go down to city only when the page changes by city, such as local search, store stock or a city ad buy, and enter the postcode inside the site when the page needs one.