Spain proxies
Spain breaks an assumption that holds in neighbouring countries: there is not one language. In Catalonia, the Basque Country and Galicia sites serve regional versions, so the city you request decides which version comes back, not only where you appear to be. That makes city targeting and sticky sessions matter more here than in most of Europe.
What we have in Spain
All four types are available. Prices are the same as in every other country we cover.
Spanish retail, local search results, ad verification
Accounts and long sessions on one address
Volume collection, routes through Madrid and Barcelona
Platforms that expect a carrier address
What Spanish addresses get used for
Retail price monitoring
El Corte Inglés, PcComponentes, MediaMarkt ES, Carrefour ES, Worten, Amazon.es: prices and stock for a Spanish shopper differ from what appears elsewhere.
Second-hand and classifieds
Wallapop, Milanuncios, Coches.net for cars, Idealista for property: local platforms rather than pan-European ones.
Fashion retail
Zara, Mango, Bershka: Spanish chains with regional storefronts that open differently depending on where the visitor arrives from.
Ad verification
El País, El Mundo, Marca, AS, 20minutos: sports titles carry more traffic here than in most of Europe.
What looks different from outside Spain
These serve a Spanish visitor something other than what a foreign one sees, because of broadcast rights and local catalogues. We sell addresses rather than a way past detection.
Which type to take for a Spanish job
Addresses in Spanish datacenters, traffic unmetered.
Volume collection, APIs, targets that ignore address class
Home connection addresses, billed per gigabyte, rotating by default.
Retail, google.es results, ad checks, regional versions
Consumer registration on datacenter hardware. Static and dedicated for the term.
Accounts, long sessions, anything that must not change address
A carrier address behind NAT, shared with real subscribers.
Social platforms and apps that expect a phone
Cities people ask for here
Cities are set with the _city_ suffix. The city matters more in Spain than in most of Europe: it drives both the regional language version of a site and part of the delivery logic.
The setups people take here most often
- 01Rotating residential, country levelPrice and search collection when regional versions are not needed.
- 02Sticky residential per cityWhen the regional version matters: Barcelona and Bilbao return a different language.
- 03Datacenter, MadridVolume jobs: cheap traffic and short routes across Iberia.
- 04Static ISPAccounts and ad verification: the address holds for the whole term.
Connection strings for Spain
The country code is ES, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Spanish static addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Spanish exits, four ways
curl -x login_c_ES:[email protected]:10000 https://api.ipify.org
# Barcelona, held for fifteen minutes on session 42
curl -x login_c_ES_city_Barcelona_s_42_ttl_15m:[email protected]:10000 https://api.ipify.org
# a Spanish static address: no suffixes
curl -x login:password@YOUR-ES-IP:50100 https://api.ipify.org
# SOCKS5 with remote DNS so the lookup is Spanish too
curl -x socks5h://login_c_ES:[email protected]:10000 https://api.ipify.orgIn Spain the language depends on the region, not only the country
This is the main difference from every other country on this list, and it breaks the familiar model where the address sets the country and the header sets the language.
Alongside Spanish, Catalan, Basque and Galician are in official use, and a significant share of sites serve regional versions: a different interface language, sometimes a different ordering of categories, occasionally different promotions. Public sector and regional sites do it almost always; large retail often.
The consequence is that in Spain the city and the language header work as a pair. A Barcelona address with es-ES returns the Spanish version, a Barcelona address with ca-ES the Catalan one, and a Madrid address with ca-ES looks contradictory and will produce unexpected results on some sites.
Practical conclusion: decide in advance which version you are collecting and keep the city and Accept-Language consistent. A dataset where half the rows were captured in Spanish and half in Catalan cannot be compared even against itself.
What actually blocks you on Spanish targets
Spain follows the familiar split, with one local twist worth planning for.
Large retail and the classifieds platforms filter hosting ranges. A datacenter address gets a 403 or a challenge, and residential is the answer.
Publishers and reference sites serve datacenter addresses normally.
The twist is that regional versions add a second reason to hold a session. A site that decides your language from the region will do it once per session, so rotating mid-job can hand you two language versions of the same dataset. Use a sticky session for the length of a run.
As everywhere, test each domain once from datacenter before committing to per-gigabyte pricing.
Which exits you get here, and how stable they are
The Spanish pool in practical terms.
Residential density concentrates in Madrid and Barcelona, with Valencia, Seville, Bilbao and Málaga behind them. Those six cover most city requests reliably; anything smaller should have a country-level fallback.
The city choice here carries more weight than in most countries because it also selects the regional language version, so a failed city request changes the content you get, not only the geography.
Sticky lifetimes behave normally and Spanish home connections are stable, so plan sessions the way you would in France or Italy.
Choosing the type for a Spanish target
The usual order. In Spain it pays more often than average to plan for a sticky session, because regional versions and the basket both span several steps.
- Start on datacenter. If the target serves you normally, stop: unmetered traffic at $1.15 per address per month.
- A 403 on the first request means hosting ranges are filtered. Move that domain to residential, leave the rest.
- A 429 after many requests is a per-address rate limit: more addresses, not a different type.
- Accounts belong on ISP: static, dedicated, Spanish consumer registration.
- Take mobile only where the platform expects carrier traffic.
What Spanish sites check beyond the address
A Spanish address opens the first gate; language, timezone and the consistency between them decide the rest.
The language header carries more meaning here than elsewhere, because there are more than two options. Send es-ES when you are collecting the nationwide version, and the regional code when that is specifically what you want.
Timezone: the mainland runs on Europe/Madrid, while the Canary Islands are an hour behind on Atlantic/Canary. A profile on a Canary address reporting Madrid time contradicts itself.
Then the usual: consent banners hide content, and a scraper that does not handle them captures an empty page under a successful status code.
What a month of Spanish work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Spanish retail, 50,000 product pages a day with images blocked, roughly 80 KB per page. That is 4 GB a day, about 120 GB a month: $120 on residential. If the targets do not filter hosting ranges, ten datacenter addresses do the same for $13.50.
- Collecting two language versions of the same pages doubles the traffic but not the address count: the same 120 GB becomes 240 GB, so $240. Decide in advance whether you need both.
- Twenty Spanish accounts on ISP addresses at $2.10 each on the volume tier: $42 a month, with no traffic billing at all.
The legal part, stated plainly
Spain applies the GDPR, with supervision by the national data protection authority. Collecting data that identifies people brings you under that regime regardless of where your company sits, and a Spanish address changes none of it.
This is general information rather than legal advice. Our terms require lawful use and we act on abuse reports. Where the answer carries commercial risk, ask a lawyer.
Verifying a Spanish exit
Under a minute. In Spain it is worth adding a check on the language of the response: the address can be right while the version of the page is not.
Three checks
# 1. is the exit Spanish, and in which city
curl -x login_c_ES_city_Barcelona:[email protected]:10000 https://ipinfo.io/json
# 2. does the sticky session hold
for i in 1 2 3; do
curl -s -x login_c_ES_s_42_ttl_15m:[email protected]:10000 https://api.ipify.org; echo
done
# 3. which language did the target actually return
curl -s -x login_c_ES:[email protected]:10000 \
-H "Accept-Language: es-ES,es;q=0.9" https://example.es | grep -o '<html[^>]*lang="[^"]*"'Questions people ask before buying Spanish addresses
Are all four types available in Spain?
Yes. Residential, ISP, datacenter and mobile are all there.
Why does the same site serve me different languages?
Because Catalan, Basque and Galician are in official use alongside Spanish, and many sites serve regional versions. Keep the city and Accept-Language consistent.
Datacenter or residential for Spanish sites?
Large retail and classifieds refuse hosting ranges and want residential. Publishers and reference sites serve datacenter normally. Test each domain once before committing to per-gigabyte pricing.
Do I need city targeting?
More often than average in Spain. The city drives not only local results but the regional language version of a site.
Do Spanish addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, datacenter from $1.15 per address per month, ISP from $1.90, mobile from $5.76 per day.
Madrid or Barcelona?
For nationwide content it makes no difference. Barcelona is worth it when you need the Catalan version or that region’s local results.