Proxy FAQ

Residential and mobile proxies billed per GB, and static ISP and datacenter IPs billed per IP. Residential has three plans: Solve (our lowest-cost residential plan), Scale and Opus.

Self-serve checkout for ISP and datacenter IPs is paused, so they are available through sales. See all products.

Create an account with an email address and password, confirmed by a one-time email code, or sign in with Google or Discord. Buy GB on a plan (from 1 GB), copy your credentials in the dashboard under Residential (or Mobile) → Generate, and send a test request. The quickstart walks through each step.

The smallest order is 1 GB, so you can test with a small purchase. See pricing.

No. netdash is a standard HTTP proxy that authenticates with a username and password, so any client that supports an authenticated HTTP proxy works without an SDK. There is no public account API. See the proxy format reference.

Residential and mobile GB are one-time purchases in USD with graduated pricing per order: each GB is charged at the rate of the band it falls into, from 1 to 50,000 GB per order. Separate orders are priced separately. The pricing page lists every band and has a calculator.

The plans differ in which network pool they route to and in price. Connection syntax is identical, so you can switch plans by changing the host and port: solve-us.netdash.io:1000, scale-us.netdash.io:2000 or opus-us.netdash.io:3000, with -eu hosts for the Europe gateway. See residential proxies.

No. Purchased residential and mobile GB never expire. See billing.

No. Each plan keeps its own GB balance, so buy GB on the plan whose host and port you connect to. Your username and password are the same on every residential and mobile plan. See billing.

You pay for the traffic you use: 1 GB of traffic is 1 GB from your balance. See billing.

No. There is no per-account concurrency or thread limit. To weigh residential and mobile against static IPs, compare proxy types.

50,000 GB is the maximum for one order. For more in one order, or for custom terms, contact sales. See enterprise for what to include.

Per IP, renewing every 30 days. Individual IPs are $1.60 (ISP) or $1.40 (datacenter); /24 subnets are $1.40 per IP, or $1.30 per IP from four subnets.

Self-serve checkout is paused. Contact sales for availability. See ISP and datacenter pricing.

For rotating sessions, send requests without session parameters and the gateway assigns exit IPs for you. For a sticky session, add -session-{SID}-ttl-{MIN} to your username, for example USERNAME-cc-DE-session-a1b2c3d4-ttl-30. Reusing the same session ID keeps the same exit IP for the TTL while that IP stays available. See sessions.

You set the lifetime in minutes with -ttl-. The dashboard offers presets of 15 minutes, 30 minutes, 12 hours and 7 days. See sessions.

Residential and mobile exit IPs are available in most countries worldwide, except very small countries and countries that restrict VPN or proxy use, for example the United Arab Emirates. Pick the exit country with its two-letter ISO code in -cc-, for example -cc-DE for Germany. See country targeting and gateways and static IP locations.

No. Targeting is country-level: you can't select a city, region, ZIP code, ASN or carrier. See country targeting.

Country codes follow ISO 3166-1 alpha-2, where the United Kingdom is GB. Use -cc-GB for UK exits. See country targeting.

netdash is an HTTP proxy. HTTPS websites are reached through the proxy with HTTP CONNECT tunnelling, so the TLS connection runs between your client and the website. See the proxy format reference.

No. Every request authenticates with your username and password. Keep them in environment variables such as NETDASH_USERNAME and NETDASH_PASSWORD rather than in code. See the proxy format reference.

Anything that supports an authenticated HTTP proxy. The integration guides cover Python, Node.js, Go, Scrapy, Selenium, Playwright, Puppeteer, Claude Code, agent frameworks and cloud browsers.

A 407 (Proxy Authentication Required) means the gateway rejected your credentials or the username syntax. Check the password, the country code after -cc- and the session parameters; session IDs use letters and digits only. See troubleshooting.

No. netdash doesn't solve CAPTCHAs, render JavaScript, retry requests or try to get past a website's access controls. A challenge reaches your client exactly as the website sent it. If you see one, slow down, check the site's terms, or stop. See responsible use.

Card payments through Stripe Checkout, in USD. See billing.

Our Refund Policy sets out which purchases qualify and how to request a refund.

Email support@netdash.io, open live chat on this site, or ask in Discord. Never send your password. The contact page lists every channel.

We don't publish uptime figures or offer an SLA. If requests fail, contact support with the time in UTC, the gateway host and port, and the error.

Yes. Affiliates earn 10% commission on referred residential and mobile purchases and 5% on ISP and datacenter purchases once self-serve checkout for them reopens, with a $50 minimum payout. See the affiliate program.

Legitimate business purposes, including data collection, market research and ad verification. Section 2 of our Terms of Service says so and lists the uses that are not allowed. Stay within the law and each website's terms, and don't collect personal data without a lawful basis. See responsible use; how we handle your own data is set out in our Privacy Policy.

Whether you can collect a given dataset depends on the site's terms, the data and your jurisdiction; get legal advice for your case. Responsible use lists the norms we expect every job to follow.