Iran · Sistan and Baluchestan · Ḩājj Ḩalīm Khān-e Sharīfābād
Buy Ḩājj Ḩalīm Khān-e Sharīfābād proxies. Ready in minutes.
Residential IPs with a Ḩājj Ḩalīm Khān-e Sharīfābād exit in Iran. 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 Iran list.
The place
Where Ḩājj Ḩalīm Khān-e Sharīfābād sits
Ḩājj Ḩalīm Khān-e Sharīfābād is the 460th-largest listed city in Sistan and Baluchestan and the 40489th-largest in Iran.
It sits 1,060 km southeast of Tehran, in the far north of Sistan and Baluchestan, 482 m above sea level.
Local clocks run on Tehran time (Asia/Tehran).
The nearest big city is Zābol, 20 km to the south.
Ḩājj Ḩalīm Khān-e Sharīfābād marked on Iran, Tehran shown for scale.
When a Ḩājj Ḩalīm Khān-e Sharīfābād exit is worth asking for
An exit in Ḩājj Ḩalīm Khān-e Sharīfābād answers a narrower question than a Iran exit. Most sites decide what to show you at the country level, and for them any Iran address is the whole answer, whether it sits here or in Tehran.
The city earns its keep when the check itself is local: what is in stock near Ḩājj Ḩalīm Khān-e Sharīfābād, what delivery gets promised, what the local results page actually shows. That is the work worth pinning to a city, and the only work that should accept city-level supply as a constraint.
City-level residential supply moves week to week everywhere, ours included. If nothing is live in Ḩājj Ḩalīm Khān-e Sharīfābād the moment you ask, the reliable fallback is a Iran exit, and the free Iran list shows the public pool measured live.
Get started
Pick your Ḩājj Ḩalīm Khān-e Sharīfābād proxy
Residential is the product with Ḩājj Ḩalīm Khān-e Sharīfābād city targeting. ISP and mobile are Iran-level options on a static or carrier IP, for when the country is enough.
Recommended for Ḩājj Ḩalīm Khān-e Sharīfābād
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 Ḩājj Ḩalīm Khān-e Sharīfābād
The closest places we also cover are Deh-e Morād (1.6 km), Deh-e Gholām-e Sharīfābād (1.7 km), Deh-e Bāshī (1.9 km). In all, 155 listed places sit within 20 km. Each has its own page and its own city-level targeting.
Need the whole Sistan and Baluchestan picture? Sistan and Baluchestan proxies.
FAQ
Ḩājj Ḩalīm Khān-e Sharīfābād proxy questions, answered
Can I get a proxy with a Ḩājj Ḩalīm Khān-e Sharīfābād IP address?
Residential plans support city-level targeting, so you can request Ḩājj Ḩalīm Khān-e Sharīfābād specifically, or widen the same request to Sistan and Baluchestan without changing plans. What is live in any one city moves constantly, for every provider; the Iran country exit is the request that never depends on one place.
Where is Ḩājj Ḩalīm Khān-e Sharīfābād?
In Sistan and Baluchestan, Iran, 1,060 km southeast of Tehran. The local timezone is Tehran time (Asia/Tehran). It lies 482 m above sea level.
Is a Ḩājj Ḩalīm Khān-e Sharīfābād IP different from any other Iran IP?
To a site that reads only the country: no. Ḩājj Ḩalīm Khān-e Sharīfābād and Tehran 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 Ḩājj Ḩalīm Khān-e Sharīfābād has nothing live when I ask?
Then take Sistan and Baluchestan as a whole, or the Iran 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.