How precise can geo-targeting get — country, city or carrier?

You can target all three simultaneously. Add -country-TR-city-istanbul-carrier-turkcell to the proxy username and the request exits via a Turkcell IP physically in İstanbul. City and carrier availability follows your owned device fleet or your configured upstream residential pool.

Do I need a separate proxy endpoint for each country?

No. One Nodetonet proxy endpoint serves every geography — you just change the username suffix per request or per session. Your scraper or bot points at the same host and port regardless of the target country.

Can I combine geo-targeting with sticky sessions?

Yes. Add -session-XXXX alongside the geo modifier — for example user-country-TR-city-istanbul-session-abc123. The same local IP is held for all requests sharing that session key, which is essential for multi-step logins, checkouts or any stateful flow that must stay on one identity.

What happens if no device matches the requested geo?

If an upstream residential provider is configured, Nodetonet forwards the request there with the same geo modifier. If no upstream is configured and no owned device matches, the connection is refused rather than silently exiting from the wrong location. This prevents accidental geo-leaks.

Does geo-targeting work with SOCKS5 as well as HTTP?

Yes. The username modifier syntax is identical on both protocols. Use HTTP/HTTPS for browser-driven requests and most scraping tools, and SOCKS5 for raw TCP connections or non-web traffic. See HTTP and SOCKS5 proxies for a full comparison.

How is geo-targeting different from using a VPN to change location?

A VPN gives you one IP at a time from a datacenter, which many sites detect and block. Geo-targeted mobile proxies give you real carrier IPs that rotate on demand, per-request geo control, and no interference with traffic outside the proxy. For stateful tasks, sticky sessions let you hold one location without a VPN.

Is carrier targeting available for Turkish operators like Turkcell and Vodafone?

Yes. Nodetonet's owned fleet includes devices on Turkcell, Vodafone and Türk Telekom in Turkey. Use -carrier-turkcell, -carrier-vodafone or -carrier-turk-telekom in your username modifier. You can further narrow to İstanbul or another city with -city-istanbul. See the Turkey location page for full details.

Geo-targeting proxies — pick the country, city or carrier of your exit IP

When you need a request to look like it came from a specific place — a city in Turkey, a Turkcell subscriber in İstanbul, or a T-Mobile user in New York — the exit IP's geography is the whole story. Nodetonet's geo-targeting lets you steer that geography precisely, without juggling separate proxy endpoints for each location. Append a modifier to your proxy username and your request leaves from a matching real mobile IP.

TL;DR: add -country-TR (or -city-istanbul, -carrier-turkcell) to your username. That's it. No endpoint swap, no extra config.

How geo-targeting works

Nodetonet reads the modifier from the proxy username at connection time and selects a paired device — or, if no owned device matches, forwards through an upstream residential pool — that satisfies the geo constraint. Because the modifier is part of the credential, your tool (scraper, browser, bot) never has to change its target host or port. One endpoint serves every geography you need.

Supported modifier format:

username-country-TR — exit from Turkey
username-country-TR-city-istanbul — exit from İstanbul, Turkey
username-country-US-city-newyork — exit from New York, USA
username-country-DE-state-bavaria — exit from Bavaria, Germany
username-carrier-turkcell — exit via a Turkcell-assigned IP
username-carrier-vodafone — exit via a Vodafone-assigned IP
username-carrier-turk-telekom — exit via a Türk Telekom IP

Modifiers compose freely: combine -country-TR-city-istanbul-carrier-turkcell to specify all three dimensions at once. See the İstanbul location page and the Turkcell carrier page for live availability details.

Two sources of geography

Geo-targeting draws from two complementary pools. Which one serves a given request depends on what your account has configured:

Your own mobile devices

Phones running the Nodetonet Android agent app are physically on a SIM in a real country on a real carrier. Each phone's exit IP is exactly where the device is — no heuristics, no IP-to-geo database lookup. You get the genuine carrier-grade NAT IP shared by thousands of real mobile subscribers on that network, which is the highest-trust address class a site can see. Because you own and operate the devices, the cost is prepaid credit on usage rather than a per-GB residential markup.

Upstream residential pool

If you need geo coverage your own fleet doesn't cover yet — a city in Germany, a carrier in Brazil — rotating proxies on Nodetonet support upstream forwarding: chain Bright Data, Smartproxy, IPRoyal or Oxylabs behind your Nodetonet proxy and pass the geo modifier through. Nodetonet remains the single stable endpoint your tools connect to; the upstream residential network delivers the city-level address. Read more in upstream residential forwarding and upstream username modifiers.

Geo-targeting modifier quick reference

Modifier	What it targets	Example value	Can combine?
`-country-XX`	ISO 3166-1 alpha-2 country code	`TR`, `US`, `DE`	Yes — with city, state, carrier
`-city-name`	City name (lowercase, no spaces)	`istanbul`, `newyork`	Yes — add country for precision
`-state-name`	State or region name (lowercase)	`bavaria`, `california`	Yes — combine with country
`-carrier-name`	Mobile carrier slug	`turkcell`, `vodafone`	Yes — combine with country/city
`-session-XXXX`	Sticky session key (hold same IP)	Any alphanumeric string	Yes — add after geo modifiers

Combining geo-targeting with rotation and sticky sessions

Geo modifiers stack cleanly on top of the rest of the rotating proxy system. Two modes are available per request:

Rotating (default): each request or timer interval picks a new device in the target location. Ideal for broad scraping, SERP checks and ad monitoring where you want many distinct local IPs. Learn when this is the right choice in rotating mobile proxies — when to use.
Sticky: append -session-XXXX alongside the geo modifier. The same local IP is held for the lifetime of that session key, letting you complete a login, cart checkout or multi-step form from a consistent address in the right city. See sticky sessions explained for the full TTL and session-key mechanics.

Per-client controls — IP whitelist, domain allow/deny lists, quota limits and thread caps — all continue to apply on top of geo-targeting. Geo is a routing layer, not a separate product.

What people use geo-targeting for

Ad verification: confirm a campaign renders correctly to real users in a specific city, carrier or country. Catch cloaked ads that hide fraud from non-local IPs. A Turkcell or Vodafone IP gives you what a Turkish mobile subscriber actually sees.
Price and inventory monitoring: e-commerce sites, airlines and hotels routinely show different prices by region. Rotating through local IPs in each market from a single proxy keeps your data collection clean and undetected.
SEO and SERP rank checking: search rankings differ by country, city and even carrier. Querying from a genuine local mobile IP gives you the same results a real local user sees, not a datacenter-adjusted view.
Localized QA and testing: test geo-gated content, currency formatting, language fallbacks and feature flags before launch. A real carrier IP bypasses VPN-detection layers that trip on datacenter ranges. Use the proxy checker tool to confirm your exit location before a test run.
Social media and multi-account management: each account should look like it lives on its own local device. Pairing a geo modifier with a sticky session creates a stable, location-consistent identity per account.
Market research and data collection: pull public data sets from local IPs to get locally cached or region-specific results without triggering geo-block or CAPTCHA walls.

Whatever the task, the principle is the same: the closer your exit IP matches the audience you are simulating, the more accurate and unobstructed your data will be. Check what is my IP after connecting to confirm the exit geography before your scraper runs.

Geo-targeting vs a VPN — what's the difference?

A VPN reroutes your entire device's traffic through a single server IP, typically in a datacenter. Sites increasingly detect and challenge datacenter IP ranges, and a VPN gives you no per-request control. A geo-targeted proxy is the opposite: you choose the country and carrier per request, the exit IP is a genuine mobile carrier address trusted by anti-bot systems, and your non-proxy traffic is unaffected. For a full breakdown, read VPN vs proxy — which to use.

Carrier-level targeting in Turkey

Turkey is one of the most active markets for mobile proxy geo-targeting. Nodetonet's owned device fleet includes phones on all three major Turkish operators — Turkcell, Vodafone and Türk Telekom — across multiple cities including İstanbul. This means you can target not just the country (-country-TR) but the exact operator and city combination that matches your audience, using real carrier CGNAT IPs rather than spoofed location metadata.

TCP/IP fingerprint and geo together

Getting the IP location right is necessary but not always sufficient. Some advanced anti-bot systems also inspect the TCP/IP stack fingerprint of incoming connections — and a datacenter OS fingerprint from an IP claiming to be a Turkish mobile subscriber raises a flag. Nodetonet's TCP/IP fingerprint spoofing aligns the connection's network-level signature with what a real Android device on the target carrier would send, so the location and the fingerprint tell the same story. This is transparent — no extra config is needed alongside geo modifiers.

Protocol support: HTTP/HTTPS and SOCKS5

Geo-targeting works across both supported proxy protocols. Use HTTP/HTTPS for browsers, scraping frameworks and most web tooling. Use SOCKS5 for raw TCP connections, game clients, custom tools and non-HTTP traffic. The geo modifier syntax is the same on either protocol. See HTTP and SOCKS5 proxies for a full protocol comparison, and HTTP vs SOCKS5 — which to pick for a decision guide.

Extending coverage with upstream forwarding

Your owned mobile fleet delivers the highest-trust, lowest-cost geo-targeting — but it is bounded by where your devices are. When you need a location your fleet doesn't cover, upstream forwarding plugs the gap without changing your endpoint or workflow. You configure an upstream provider's credentials once in the Nodetonet panel, and the geo modifier is automatically relayed to that provider on any request that doesn't match your own fleet. The upstream provider carries the address; Nodetonet carries the auth, quota enforcement, client isolation and rotation logic. See upstream-only proxies and sticky upstream sessions for setup details.

Get started

Create a free account and add prepaid credit — no monthly subscription required.
Pair an Android device via the agent app (see your first token and Android pairing) or configure an upstream residential provider for global city coverage.
Create a mobile proxy or rotating proxy in the panel.
Append the geo modifier to the proxy username — for example yourtoken-country-TR-city-istanbul-carrier-turkcell.
Send your request. The exit IP matches the target location. Verify with what is my IP if needed.

Questions? Reach the team on Discord or email. For a broader view of what Nodetonet offers, start with the all features overview.