Austria proxies
Austria gets treated as a small Germany, and that is where the data goes wrong. A large share of Austrian commerce runs on German domains, where the country is decided by the visitor’s address rather than the site’s. Then there is the language: Austrian German differs from the German of Germany in vocabulary rather than accent, and keyword lists built for Germany miss a good part of local demand.
What we have in Austria
Prices are the same as in every other country we cover.
What Austrian addresses get used for
Retail price monitoring
Interspar, Billa, MediaMarkt.at, Shöpping, plus the German domains that serve Austria off the buyer’s address.
Classifieds and second-hand
Willhaben covers here what three separate platforms usually split elsewhere: goods, cars and property.
Price comparison
Geizhals keeps separate listings for Austria and Germany, and the prices diverge routinely.
Local search and SEO
google.at: Austrian results are their own set, and the query vocabulary does not match the German one.
What looks different from outside Austria
These serve an Austrian 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 an Austrian job
Home connection addresses, billed per gigabyte, rotating by default.
Retail, search results, classifieds, ad checks
Consumer registration on server 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.
Apps and platforms that expect a phone
Cities people ask for here
Cities are set with the _city_ suffix. Vienna outweighs the rest, but Graz, Linz and Salzburg resolve reliably.
The setups people take here most often
- 01Residential, country levelThe default for retail, search results and classifieds.
- 02An ISP address for the termWhen you need the same address for weeks and would rather not count traffic.
- 03Mobile addressApps and platforms expecting a carrier.
- 04Austria apart from GermanyTwo passes over the same domains, because the conditions there differ.
Connection strings for Austria
The country code is AT, upper case. The city goes after it with _city_, hyphens instead of spaces, in the order country, city, session, lifetime.
Austrian ISP addresses take no suffixes: the host is the IP from your dashboard, port 50100, SOCKS5 on 50101.
Austrian exits, four ways
curl -x login_c_AT:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# held for fifteen minutes on session 42
curl -x login_c_AT_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# Graz explicitly, when you are comparing regions
curl -x login_c_AT_city_Graz_s_43_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org
# an Austrian ISP address: no suffixes
curl -x login:password@YOUR-AT-IP:50100 https://api.ipify.orgThe same domain, a different country
The most common mistake in Austria, and it has nothing to do with blocking.
Several large platforms have no separate Austrian domain: Austrians buy on German sites, and the country is decided by the visitor’s address. The same URL gives a German and an Austrian visitor different delivery terms, different lead times, sometimes a different range and a different price.
The consequence breaks estimates: you cannot collect a German domain once and label the result "Germany and Austria". It is two passes over identical links from different addresses, and the data in them diverges.
A minute settles it: open one product page from a German exit and from an Austrian one, then compare the delivery block. If it differs, half of everything you have exported from that domain was German.
The reverse happens too: some Austrian chains keep a domain in the at zone while also serving German buyers. One rule covers both cases. The country is set by the address, not by the domain zone.
Austrian German is its own vocabulary
The second difference from Germany, and it hits keyword lists and product matching.
The divergence is in words rather than accent. January here is Jänner, not Januar. Potatoes are Erdäpfel, tomatoes Paradeiser, a bread roll a Semmel, a bag a Sackerl. In retail catalogues that means the same product carries different names on either side of the border.
For search collection this means a keyword list built on Germany understates Austrian demand, because part of the market types its own words. Positions against that list look respectable while the traffic is not there.
For price monitoring it means matching German and Austrian catalogues by product name produces false misses. Match on article number or product code instead, and treat the name as a hint rather than a key.
Send de-AT rather than de-DE while you are at it: some platforms switch both wording and regional offers on that header.
What actually blocks you on Austrian targets
The familiar Western European split.
Retail chains and Willhaben filter server ranges and expect a home address: residential or ISP.
Publishers and government sites serve requests calmly and rarely cause trouble.
Apps and the platforms grown out of them sometimes expect a carrier address: that is where mobile helps.
Search results are reachable but rate limited per address: more addresses rather than a different type.
Which exits you get here, and how stable they are
The Austrian pool in practical terms.
The pool is small: a country of nine million people, and it shows. Enough for monitoring, search and ad checks; not enough for jobs needing thousands of concurrent addresses.
Line quality is excellent and even, response times from Germany and Switzerland are short and from the rest of Europe predictable.
Vienna outweighs the rest, but Graz, Linz and Salzburg resolve reliably, so regional comparisons are genuinely possible here, unlike in countries with one live city.
Sticky sessions behave normally. ISP addresses do not rotate at all, and mobile rotates by physical reconnect: seconds rather than milliseconds.
Choosing the type for an Austrian target
The order here is shorter than usual.
- Start with country-level residential: it passes on retail and classifieds, and you pay only for the gigabytes you pull.
- If the work lives on one address for weeks, count gigabytes. Above two gigabytes a month on a session, ISP at $1.90 is already cheaper.
- If the target is an app and residential runs into a check, try a mobile address.
- A 429 after many requests is a per-address rate limit: more addresses, not a different type.
- Ask for a city only when comparing regions. Otherwise country level is more reliable.
What Austrian sites check beyond the address
Language is covered above; here is the rest.
The currency is the euro and the number format is German: 1.299,90 €, a dot for thousands and a comma for decimals. A parser written for the English format reads that as one thousand two hundred ninety nine point nine.
There is one time zone, CET, and it shifts in summer. Configure the profile to it rather than to UTC.
Dates run day-month-year, and Austrian text uses Jänner regularly: date parsing against a German month list trips over it.
Consent banners are mandatory and cover the content: a scraper that does not handle them captures an empty page under a successful status code.
What a month of Austrian work costs
Three scenarios at our prices, so you have something to check a quote against.
- Price monitoring across Austrian retail, 20,000 listings a day with images blocked, roughly 110 KB per page. That is about 2.2 GB a day, around 66 GB a month: $66 on residential.
- The same domains on a second pass from a German exit double the volume: about $132 a month for both markets. That is the price of not passing German terms off as Austrian ones.
- Five ISP addresses for long sessions cost $9.50 a month with traffic unmetered.
The legal part, stated plainly
Austria is in the European Union, so GDPR applies here with everything that follows for collecting personal data. An Austrian address neither puts you under it nor takes you out: what matters is whose data you collect, not where the traffic exits.
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 an Austrian exit
Under a minute. The second command matters more than the first: it shows that a German domain is treating you as Austrian.
Three checks
# 1. is the exit Austrian, and where
curl -s -x login_c_AT:password@proxy.sotaproxy.com:10000 https://ipinfo.io/json
# 2. the same German domain, two countries
curl -s -H "Accept-Language: de-DE" -x login_c_DE:password@proxy.sotaproxy.com:10000 https://your-target.de/product | grep -i "versand" | head -3
curl -s -H "Accept-Language: de-AT" -x login_c_AT:password@proxy.sotaproxy.com:10000 https://your-target.de/product | grep -i "versand" | head -3
# 3. does the sticky session hold
for i in 1 2 3; do
curl -s -x login_c_AT_s_42_ttl_15m:password@proxy.sotaproxy.com:10000 https://api.ipify.org; echo
doneQuestions people ask before buying Austrian addresses
Will a German address do for Austria?
No, and this is the main mistake in this country. On German domains the country is decided by the visitor’s address, so a German exit collects German delivery terms and prices.
Why send de-AT instead of de-DE?
Some platforms switch wording and regional offers on that header. Beyond that, Austrian vocabulary differs from the German one, and that shapes search results.
Residential or ISP?
Count gigabytes. One-off wide-coverage passes are cheaper on residential; work that stays on one address for weeks is cheaper on ISP at $1.90 a month.
How large is the Austrian pool?
Small: a country of nine million people. Fine for monitoring and ad checks, not for thousands of concurrent addresses.
Can I compare regions?
Yes. Vienna outweighs the rest, but Graz, Linz and Salzburg resolve reliably, so a regional sample is realistic here.
Do Austrian addresses cost more?
No. Prices are the same everywhere: residential from $1.00 per GB, ISP from $1.90 per address per month, mobile from $5.76 per day.