- New York City
USERNAME-country-us-city-new_york - Los Angeles
USERNAME-country-us-city-los_angeles - Chicago
USERNAME-country-us-city-chicago - Houston
USERNAME-country-us-city-houston - Dallas
USERNAME-country-us-city-dallas - Miami
USERNAME-country-us-city-miami - Atlanta
USERNAME-country-us-city-atlanta - Seattle
USERNAME-country-us-city-seattle - San Francisco
USERNAME-country-us-city-san_francisco - Boston
USERNAME-country-us-city-boston - Phoenix
USERNAME-country-us-city-phoenix - Denver
USERNAME-country-us-city-denver
Choose a US city
Each city page below shows the exact token for that metro, the gateway ports and what the targeting does and does not cover. City cards appear below this guide; use them to jump to the market you need.
How US city targeting works
City targeting is part of the proxy username. Take your credentials, add the country and city tokens, and connect to gw.nefo.net:
USERNAME-country-us-city-new_york
USERNAME-country-us-city-los_angeles
USERNAME-country-us-city-san_franciscoMulti-word cities use an underscore, so New York City is new_york. Port 9000 returns a new IP on every request, and port 10000 keeps one IP for a sticky session of 1 minute to 24 hours. HTTP, HTTPS and SOCKS5 are all supported. The dashboard generator builds the string, and the docs list the full token syntax.
What city-level targeting covers
Targeting is at the metro level, not ZIP code or neighborhood. You reach residential IPs inside the chosen metro, but Nefo does not guarantee a particular borough, suburb or postal code. That is enough for most local price, ad and search checks, where the aim is to see the version of a page a local visitor gets.
What people use US city proxies for
- Local price monitoring across retail and marketplace listings in a given metro.
- Verifying that geo-targeted ads and promotions reach the intended audience.
- Localized SEO and SERP checks, for example comparing Seattle and Miami results.
- Market research on region-specific catalogs and availability.
Keep all use lawful, limited to public data and within each site's terms and the acceptable use policy.
Pick a city, then compare markets
Because only the city token changes, the same scraper or browser profile can run against several metros in turn. A common pattern is to choose two or three markets, for example New York City and Chicago, or Los Angeles and Seattle, run an identical price or SERP check from each and compare the output. Use rotating sessions on port 9000 for broad sampling, and sticky sessions on port 10000 when a check walks through several pages on one site.
If you need a city that is not on this list, generate credentials in the dashboard and set the city there, or read the US city-targeted proxies guide for how city selection behaves across the US.
Pricing for US residential proxies
City targeting uses the same residential balance as every other location. Packages start at $4.50 for 5 GB ($0.90/GB), reach $0.73/GB at 100 GB and $0.53/GB at 10 TB, and the bandwidth never expires. Credentials are free, so you pay only for the traffic you use. Compare packages on the pricing page.
Frequently asked questions
The twelve city pages cover New York City, Los Angeles, Chicago, Houston, Dallas, Miami, Atlanta, Seattle, San Francisco, Boston, Phoenix and Denver. You can also target any US city when you generate credentials in the dashboard generator.
Append the country and city tokens, for example USERNAME-country-us-city-chicago, and connect to gw.nefo.net. Port 9000 rotates on every request and port 10000 gives sticky sessions. See the docs for the full syntax.
No. Targeting is at the metro level. You get residential IPs inside the chosen city's metro, but a specific borough, suburb or postal code is not guaranteed.
Residential bandwidth starts at $4.50 for 5 GB ($0.90/GB) and falls to $0.53/GB at 10 TB. City targeting is not billed separately and the bandwidth never expires. See pricing.
A sticky session holds one IP from 1 minute up to 24 hours, using port 10000. Rotating sessions on port 9000 take a new IP on every request.