A quick check with cURL confirms your credentials and country before you add the proxy to a scraper or test suite:
curl -x gw.nefo.net:9000 \
-U "USERNAME-country-us-city-losangeles:PASSWORD" \
https://api.ipify.org?format=jsonGateway, ports and username tokens
All guides connect to gw.nefo.net. The port decides the protocol and whether the exit IP rotates or stays put:
| Port | Protocol | IP behavior |
|---|---|---|
| 9000 | HTTP | New IP on every request |
| 10000 | HTTP | Sticky session, one IP from 1 minute up to 24 hours |
| 11000 | SOCKS5 | New IP on every request |
| 12000 | SOCKS5 | Sticky session, one IP from 1 minute up to 24 hours |
Targeting lives in the username. Add -country-us for a country, further tokens for US state and city or an ASN, and -session-<id> with a lifetime such as -lifetime-30 to hold a sticky IP. Generate credentials for free in the proxy generator in your dashboard; only routed traffic uses your prepaid bandwidth.
Which integration guide should I use?
- Python scripts and APIs: Python Requests, or Scrapy for full crawls.
- Browser automation: Puppeteer, Playwright or Selenium. Chromium cannot authenticate SOCKS5, so use the HTTP ports with Puppeteer and Playwright.
- Node.js, Go, Java and PHP services: Node.js Axios, Go, Java and PHP.
- Quick tests from a terminal: cURL.
Rotating or sticky sessions
Use a rotating port when each request can come from a different IP, such as wide crawls. Use a sticky port with a session token when a login, cart or multi-step flow must stay on one IP. The rotating proxies and sticky session proxies pages explain both, and the docs list the full connection reference.
Antidetect browsers and other tools
Using a profile-based browser or a tool that is not a code library? The partners page has setup steps for antidetect browsers, cloud phones, captcha solvers and data tools.
Frequently asked questions
Point your HTTP client or browser at gw.nefo.net on port 9000 (rotating) or 10000 (sticky), and send your proxy username and password. Pick your language from the guides above for a working example.
HTTP port 9000 and SOCKS5 port 11000 rotate the IP on every request. HTTP port 10000 and SOCKS5 port 12000 hold one IP for a session you control. Add a -session- token to the username on the sticky ports.
Add a country token, for example USERNAME-country-us. US state and city, and ASN, use further tokens in the same username. The code around it does not change, so one template serves every region.
Python Requests, Node.js Axios, Go, Java, PHP, cURL, Scrapy and Selenium can use SOCKS5 on ports 11000 and 12000 with the right library or option. Chromium cannot authenticate SOCKS5, so use the HTTP ports with Puppeteer and Playwright.
No. Credentials are free to generate, and only the traffic you route through the proxy uses your prepaid bandwidth. See residential proxy pricing for the package sizes.
The API and connection docs cover the gateway, ports, authentication and the REST API for proxies and usage.