Afghanistan · Samangan · Kārtah-ye Khurāsān
Buy Kārtah-ye Khurāsān proxies. Ready in minutes.
Residential IPs in Kārtah-ye Khurāsān, a district of Aībak we track separately. Pay as you go, no subscription, and a balance that never expires. From $0.44/GB.
Just need a few free ones? Browse the live free Afghanistan list.
The place
Kārtah-ye Khurāsān is part of Aībak
Kārtah-ye Khurāsān is not a separate city: it is a district of Aībak, on the west side of the city. See Aībak proxies.
We list it because people search for it and because per-IP geolocation sometimes resolves to the district rather than the city. For every practical purpose an address here is a Aībak address, and the Aībak page carries the fuller picture.
Kārtah-ye Khurāsān marked on Afghanistan, Aībak shown for scale.
When a Kārtah-ye Khurāsān exit is worth asking for
For most sites, an IP address here identifies as Afghanistan first and Kārtah-ye Khurāsān second. Checks that stop at the country, and that is prices, catalogs, language and most geo-blocks, behave the same whether your exit sits in Kārtah-ye Khurāsān or in Aībak.
City targeting starts to matter when the question is genuinely local: store stock and pickup, delivery estimates, local search results, regional pricing, or anything a map decides for you. If that is your task, ask for Kārtah-ye Khurāsān specifically. If it is not, the country exit is cheaper and far more stable.
City-level residential supply moves week to week everywhere, ours included. If nothing is live in Kārtah-ye Khurāsān the moment you ask, the reliable fallback is a Afghanistan exit, and the free Afghanistan list shows the public pool measured live.
Get started
Pick your Kārtah-ye Khurāsān proxy
Residential is the product with Kārtah-ye Khurāsān city targeting. ISP and mobile are Afghanistan-level options on a static or carrier IP, for when the country is enough.
Recommended for Kārtah-ye Khurāsān
Residential Proxies
- Real household connections
- Rotate per request or hold a sticky session
- Country, state and city targeting
- Pay per GB, traffic never expires
- SOCKS5 and HTTP
ISP Proxies
- Static residential IPs from real ISPs
- Unlimited traffic on every IP
- Yours alone, never shared
- Datacenter speed, household identity
- SOCKS5 and HTTP
Mobile Proxies
- Real carrier IPs on 5G and 4G
- Auto-rotate on your schedule
- The highest trust tier against blocks
- Shared and dedicated variants
- SOCKS5 and HTTP
Nearby
The closest cities to Kārtah-ye Khurāsān
The closest places we also cover are Aībak (0.5 km), Zinḏêy Kōṯ (0.8 km), Qōs Āsyā (1 km). In all, 37 listed places sit within 20 km. Each has its own page and its own city-level targeting.
Need the whole Samangan picture? Samangan proxies.
FAQ
Kārtah-ye Khurāsān proxy questions, answered
Can I get a proxy with a Kārtah-ye Khurāsān IP address?
Residential plans support city-level targeting, so you can request Kārtah-ye Khurāsān specifically, or widen the same request to Samangan without changing plans. What is live in any one city moves constantly, for every provider; the Afghanistan country exit is the request that never depends on one place.
Is Kārtah-ye Khurāsān a city of its own?
No. Kārtah-ye Khurāsān is a district of Aībak. To any site you visit, an IP here is a Aībak address; the split only exists in geolocation databases. If you are choosing a target, Aībak is the meaningful unit.
Is a Kārtah-ye Khurāsān IP different from any other Afghanistan IP?
To a site that reads only the country: no. Kārtah-ye Khurāsān and Aībak look identical there. To anything local, map results, stock, delivery estimates, the city is exactly the difference, and that is the one case worth paying the supply constraint for.
What if Kārtah-ye Khurāsān has nothing live when I ask?
Then take Samangan as a whole, or the Afghanistan country exit. Single-city supply is fluid in this whole industry, and we would rather hand you the wider fallback in one click than promise a specific street and miss.
Place data: GeoNames (CC BY 4.0). Map outline: Natural Earth. Population figures are the dataset's listed values, not proxy counts.