# Dedicated proxy guide: types, protocols, auth and 7 countries URL: https://cloudj.net/blog/dedicated-proxy-guide Published: 2026-11-11 ยท Updated: 2026-11-11 > Everything to know before you buy a dedicated proxy: static ISP vs static residential, HTTP vs SOCKS5, password vs IP whitelist, terms and 7 countries. A dedicated proxy is an IP address that is assigned to you alone. Nobody else sends traffic through it, so its reputation and behaviour depend on how you use it, not on what strangers did with it yesterday. Cloudj sells dedicated proxies in seven countries, in two types, over two protocols, with two ways to authenticate. This guide explains each of those choices in plain terms, shows how ordering and renewal work, and links to the deeper articles for each country and use case. ## What "dedicated" means, and when it matters Proxies come in roughly three sharing models: shared (many customers use the same IP), rotating (your traffic moves across a pool of IPs) and dedicated (one IP, one customer). Cloudj sells the dedicated model only. Dedicated is the right choice when you need a stable identity: the same IP every time you log in to a seller dashboard, an IP you can add to a partner's allowlist, or a fixed address per account for a social media team. It is the wrong choice when you need thousands of different IPs per hour for large-scale crawling; that pattern calls for rotation, which we do not offer. The articles on [dedicated vs shared proxies](https://cloudj.net/blog/dedicated-vs-shared-proxy) and [static vs rotating proxies](https://cloudj.net/blog/static-vs-rotating-proxy) go into the trade-offs. ## Two types: dedicated IPv4 (static ISP) and static residential ISP Both Cloudj proxy types use IPs registered to an internet service provider (ISP), not to a datacenter or hosting range. They differ in what kind of ISP connection the address comes from. | | Dedicated IPv4 (static ISP IP) | Static residential ISP | |---|---|---| | Where the IP comes from | A static IP registered to an ISP | A home-broadband ISP | | Strength | Fast and stable | Looks like a regular user | | IP changes | No, assigned to you only | No, stays the same | | Countries | All 7 | United States and Vietnam only | | Typical use | Scraping, monitoring, automation, allowlisting, QA | Account management and local work where a home-user connection fits the task | The dedicated IPv4 static ISP proxy suits most technical work and is the only type in Japan, South Korea, Singapore, Hong Kong and the UK. Static residential ISP is worth considering in the US or Vietnam when your workflow is built around a consumer connection, such as managing accounts the way a local user would. Neither type prevents bans; how you behave on a platform matters far more than the IP, so follow each platform's rules. Read [datacenter vs ISP proxies](https://cloudj.net/blog/datacenter-vs-static-isp-proxy) for how both compare with the generic datacenter category, and the dedicated pages for [Vietnam static residential](https://cloudj.net/blog/vietnam-static-isp-proxy) and [US static ISP](https://cloudj.net/blog/us-static-isp-proxy) proxies. ## Seven countries | Country | Dedicated IPv4 (static ISP) | Static residential ISP | Guide | |---|---|---|---| | Vietnam | Yes | Yes | [Buy a Vietnam proxy](https://cloudj.net/blog/buy-vietnam-proxy) | | United States | Yes | Yes | [Buy a US proxy](https://cloudj.net/blog/buy-us-proxy) | | Japan | Yes | No | [Japan proxy](https://cloudj.net/blog/japan-proxy) | | South Korea | Yes | No | [South Korea proxy](https://cloudj.net/blog/south-korea-proxy) | | Singapore | Yes | No | [Singapore proxy](https://cloudj.net/blog/singapore-proxy) | | Hong Kong | Yes | No | [Hong Kong proxy](https://cloudj.net/blog/hong-kong-proxy) | | United Kingdom | Yes | No | [UK proxy](https://cloudj.net/blog/uk-proxy) | Stock can change, and a location can be temporarily unavailable; the console shows what is in stock right now. Product pages: the [proxy overview](https://cloudj.net/proxy-ipv4), [US proxies](https://cloudj.net/proxy-ipv4/united-states) and [Vietnam proxies](https://cloudj.net/proxy-ipv4/vietnam). ## Protocols: HTTP or SOCKS5 Each proxy works over HTTP or SOCKS5, where the location supports it, and you can switch the protocol of an order in the console. - **HTTP** is understood by browsers, `curl`, most scraping libraries and operating-system proxy settings. It is the simplest choice for web traffic. - **SOCKS5** works at a lower level and carries any TCP connection, which suits tools that are not HTTP clients. Cloudj proxies do not carry UDP. If you are not sure, start with HTTP. [SOCKS5 vs HTTP proxy](https://cloudj.net/blog/socks5-vs-http-proxy) explains when the difference matters. ## Authentication: password or IP whitelist By default every proxy uses a username and password. Alternatively, you can add an IP whitelist of up to 20 addresses; whitelisting replaces password access, so only connections from those addresses are accepted. - Use **password auth** when you connect from changing networks: laptops, phones, home connections. - Use an **IP whitelist** when you connect from fixed servers, such as a VPS running a scraper. There are no credentials in your code to leak. Passwords can be rotated from the console, and the old password stops working. Each time credentials are viewed, the view is logged and you get a notice, which helps teams notice unexpected access. See [proxy authentication: whitelist vs password](https://cloudj.net/blog/proxy-authentication-whitelist-vs-password). ## Testing a proxy in one minute The console shows host, port, username and password for each proxy. Test with `curl` before you configure anything else: ```bash # HTTP proxy with password auth curl -x http://USER:PASS@HOST:PORT https://ifconfig.me # SOCKS5 proxy, resolving DNS through the proxy curl -x socks5h://USER:PASS@HOST:PORT https://ifconfig.me ``` If the output shows the proxy's IP, it works. [Testing a proxy with curl](https://cloudj.net/blog/test-proxy-curl) covers error messages, and there are setup guides for [Chrome and Firefox](https://cloudj.net/blog/setup-proxy-chrome-firefox), [Windows and macOS](https://cloudj.net/blog/setup-proxy-windows-macos) and [Android and iPhone](https://cloudj.net/blog/setup-proxy-android-iphone). ## Ordering, terms and renewal - **Self-service.** Order in the [console](https://app.cloudj.net), pay from your account balance, and proxies are ready in a few minutes. - **Quantity.** Order 1 to 1,000 IPs at once. Larger orders get a lower price per IP through quantity tiers; [how many proxies you need](https://cloudj.net/blog/how-many-proxies-do-i-need) helps you size an order. - **Terms.** 1, 3, 6 or 12 months. Auto-renew from balance keeps the same proxies running. - **Safety nets.** If an order cannot be set up, the full amount returns to your balance. Within 24 hours of ordering you can stop an order and get the unused part back. - **Prices.** Sold at a list price per IP per month, shown live in the console before you pay. Vietnamese customers can top up the USD balance by bank transfer in VND. ## Common use cases - **Web scraping and data collection.** Pair a proxy with a US server; see [web scraping from a US VPS](https://cloudj.net/blog/web-scraping-vps-united-states), [Python scraping with proxies](https://cloudj.net/blog/python-scraping-proxy) and [Playwright and Puppeteer](https://cloudj.net/blog/playwright-puppeteer-proxy). - **E-commerce sellers.** A stable Vietnamese IP for seller centres; see [proxies for e-commerce sellers in Vietnam](https://cloudj.net/blog/ecommerce-seller-proxy-vietnam). - **Marketing teams.** [Social media agencies](https://cloudj.net/blog/social-media-agency-proxy), [Facebook Ads](https://cloudj.net/blog/facebook-ads-proxy) and [antidetect browsers](https://cloudj.net/blog/antidetect-browser-proxy). - **Monitoring.** [Local SEO rank tracking](https://cloudj.net/blog/local-seo-rank-tracking-proxy), [ad verification](https://cloudj.net/blog/ad-verification-proxy) and [UK price monitoring](https://cloudj.net/blog/price-monitoring-proxy-uk). - **Engineering.** [App QA and geo testing](https://cloudj.net/blog/app-qa-geo-testing-proxy) and [static IPs for allowlisting](https://cloudj.net/blog/static-ip-allowlisting-proxy). In every case, follow the rules of the platform you work with. ## Proxy, VPN or your own server? A proxy routes selected applications; a VPN routes a whole device. Read [proxy vs VPN](https://cloudj.net/blog/proxy-vs-vpn) if that is your question. You can also run a proxy on a [cloud server](https://cloudj.net/cloud-servers) yourself; [own proxy on a VPS vs a dedicated proxy](https://cloudj.net/blog/own-proxy-on-vps-vs-dedicated-proxy) compares the effort and flexibility. ## FAQ ### Which countries offer static residential proxies? The United States and Vietnam. Dedicated IPv4, the static ISP IP, is available in all seven countries, subject to stock. ### Is a Cloudj dedicated proxy shared, or a datacenter IP? Neither. Each IP is assigned to one customer only, and the dedicated IPv4 addresses are static IPs registered to an ISP rather than a datacenter range. ### Can I change from HTTP to SOCKS5 later? Yes. You can switch the protocol of an order in the console, where the location supports it. ### What happens when my term ends? With auto-renew on and enough balance in your account, the same proxies keep running into the next term. ### Will a dedicated proxy stop my accounts from being banned? No proxy can promise that. A clean, dedicated IP removes one risk, but platforms judge behaviour. Follow each platform's rules. ## Get your proxies Decide the country, the type (dedicated IPv4 static ISP or static residential ISP), the protocol and how you will authenticate. Then sign in to the [Cloudj console](https://app.cloudj.net), check the live per-IP price for your country, place the order and test it with `curl` a few minutes later.