Configure any available plan and add-ons. Pay only for 48 hours.
Try proxiesTLS proxies with a dedicated certificate on every IP — the hop to the proxy is encrypted, with no content logging on our end.
“HTTPS proxy” means two different things, and the gap between them is an unencrypted hop. In the usual market sense, it is a proxy that supports CONNECT: it tunnels encrypted traffic while TLS runs end-to-end from your browser to the site. But the step from you to the proxy is often plain HTTP — an observer on your network can see which domains you hit, and proxy credentials travel in cleartext. Most providers sell that setup and never mention the open segment.
Our HTTPS proxies encrypt that segment too: each IP has its own TLS certificate, and the client→proxy path is closed with TLS. Nothing crosses that hop in the clear — no domains, no credentials leaking to your ISP or a café Wi-Fi operator. Anonymous SSL proxies in this sense matter when you work from someone else’s network or do not want your provider to see target hostnames at all. One honest caveat: not every client supports TLS to the proxy — check compatibility before a large order. Regular HTTP mode on the same addresses is still there when your stack needs it (HTTP/2 is supported on that path). Port numbers for both modes are in the Dashboard.
Specs are in the adjacent panel; datacenter packages start at $19/mo, static ISP plans from $33/mo when residential-level trust matters more than per-IP price.
Four proxy protocols — how they differ and when to use each one.
| HTTP | This page HTTPS |
SOCKS4 | SOCKS5 | |
|---|---|---|---|---|
| Traffic encryption | ✕ No TLS to the proxythe proxy connection is unencrypted | ✓ TLS tunnelto our server and the target site | Depends on the application protocolHTTPS traffic remains encrypted | Depends on the application protocolHTTPS traffic remains encrypted |
| Header handling | May add or modify HTTP headers | TunneledHTTP headers inside the tunnel are not modified | Passes application traffic unchanged | Passes application traffic unchanged |
| TCP / UDP | TCP | TCP | TCP | TCP + UDP |
| Username/password auth | ✓ Supported | ✓ Supported | ✕ No password authentication | ✓ Supported |
| Remote DNS resolution | Client-dependent | Client-dependent | ✕ Nothe client resolves the hostname | ✓ Supportedwhen the client sends the hostname to the proxy |
| When to choose it | Web and API traffic, especially with software that supports HTTP proxies | When you need a TLS-encrypted connection to the proxy | Legacy software that only supports SOCKS4 | General-purpose applications, gaming, streaming, and UDP traffic |
| HTTP, HTTPS, SOCKS4, and SOCKS5 are included with every static proxy plan. Rotating plans support HTTP and SOCKS5. Buy now | ||||
Copy the example for your stack, or paste it into your AI coding assistant for help adapting it to your project.
# HTTP or HTTPS proxy curl -x http://login:password@IP:port https://example.com # SOCKS5 curl --socks5-hostname IP:port \ --proxy-user login:password \ https://example.com
import requests proxy = "http://login:password@IP:port" # your proxy from the Dashboard r = requests.get( "https://example.com", proxies={"http": proxy, "https": proxy}, ) print(r.status_code)
import { ProxyAgent } from "undici"; const dispatcher = new ProxyAgent("http://login:password@IP:port"); const res = await fetch("https://example.com", { dispatcher }); console.log(res.status);
$ch = curl_init("https://example.com"); curl_setopt($ch, CURLOPT_PROXY, "IP:port"); curl_setopt($ch, CURLOPT_PROXYUSERPWD, "login:password"); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $response = curl_exec($ch);
Choose a standard format or create a custom one with any field order and delimiter your software requires.
See the FAQ for the ports used by each protocol.
You can automate purchases, renewals, whitelist changes, and proxy list exports. Create an API key in your Dashboard in a couple of clicks.
Claude, Cursor, and other agents buy proxies, renew plans, and export updated proxy lists through an access token you create in your Dashboard. See how it works.
Per-IP prices shown are for the largest package size. Get an exact quote in the calculator above.
| IP | Country | Port | Protocol | |
|---|---|---|---|---|
| 112.64.135.45 | CN | 8080 | HTTPS | |
| 125.209.108.83 | PK | 3128 | HTTPS | |
| 114.236.137.41 | CN | 21000 | HTTPS | |
| 88.198.212.91 | DE | 3128 | HTTPS | |
| 43.98.172.166 | SG | 3128 | HTTPS | |
| 152.53.183.107 | DE | 8081 | SOCKS5 | |
| 8.211.170.91 | JP | 14680 | HTTPS | |
| 123.119.179.101 | CN | 8888 | HTTPS | |
| 195.158.8.123 | UZ | 3128 | HTTPS | |
| 110.242.70.68 | CN | 443 | HTTPS |
A few service metrics—and feedback from our customers.
The site shows itself very well. Proxies work consistently, none of them failed. Technical support quickly responded to my questions, which also pleased me. I must give it a high five!
I sell kitchens on bulletin boards and constantly have to buy proxies. I have already bought more than 100 servers for accounts, none have been blocked. The proxies are great.
For such a low price the percentage of broken proxies is very low (about 10%). I liked the presence of many subnets, the stability of the connection, and the free change of the pool every eight days.
I took proxies for Ukraine. I need proxy servers for my social networks. The admins advised me how to use proxies effectively in order not to ban my accounts. The proxies themselves work well and the prices are as adequate as possible.
Can't find your answer? Message us in live chat — real humans reply.
The segment to the proxy. At most services the path is open HTTP until the CONNECT tunnel starts — the target domain is visible in the CONNECT request, and proxy credentials sit in a Proxy-Authorization header anyone on the path can read. A proxy with TLS in the literal sense closes that hop: your client negotiates TLS with the proxy IP itself, and nothing leaves your machine unencrypted. Here that is not a separate product — a certificate is registered on each IP.
No — use regular HTTP mode on the same addresses. Page content on https sites is still protected by end-to-end TLS to the destination; only the service hop to the proxy stays open. Whether that matters depends on where you run: your own server or home network — often fine; public Wi-Fi, hotels, or a shared office — switch to true HTTPS mode. curl supports it with an https:// proxy URL; modern browsers handle it natively. Test compatibility with a paid 48-hour trial before you scale up.
Yes, natively on both — no extra apps, unlike SOCKS on iOS. iPhone: Settings → Wi-Fi → the ⓘ next to your network → Configure Proxy → Manual, then enter the address and port. The setting is per-network: each Wi-Fi network keeps its own proxy, and cellular data is not covered. On a Mac the path is the same as for the HTTP proxy setup — just turn on “Secure web proxy (HTTPS)” instead of the plain web proxy. One naming trap: Apple’s “secure” describes which traffic the proxy handles (https:// URLs), not an encrypted proxy connection to it. For the TLS-protected hop this page is about, use a client that supports that mode explicitly — the system fields don’t promise it.
Because an honest proxy does not terminate site TLS: the destination certificate passes through the tunnel untouched, so the browser check still matches. With our setup there are two certificates in play — the proxy’s (encrypts the hop to us) and the site’s (encrypts the content) — and they do not interfere. If the browser warns about the site certificate itself, that is a sign of interception in the middle — corporate filters and malicious nodes do that. A legitimate proxy service does not.
Same family, different era: SSL is the old name for what has been called TLS since 1999; people still search “ssl proxy.” The name is not the product — ask whether the client→proxy hop is encrypted. CONNECT compatibility alone is not the same as a TLS certificate on the proxy IP. We provide the second: one certificate per IP, included with every plan.
A secure HTTPS proxy server covers three things: your source IP is hidden from the target site, access to the proxy is locked with IP whitelisting, and the path to the proxy is encrypted so domains and credentials have nowhere to leak on the wire. No proxy fixes browser fingerprinting, request pacing, or behavioral bans — and the provider still sees which domains you connect to, which is a trust question, not a protocol trick. There is no magic layer beyond that.
A different proxy type may be a better fit for your use case. All products use the same Dashboard and support team.
An IP reserved exclusively for you, available from a single IP. Speeds of up to 500 Mbps per proxy.
Learn moreStatic ISP-registered residential IPs for use cases where network origin matters.
Learn morePay per request and access the full 100,000+ IP pool through a single gateway. Built for web scraping and API workloads.
Learn moreSOCKS5 with UDP support — for gaming, streaming, and VoIP.
Learn moreWe can sign a contract and provide all the documents your accounting team needs. Most business orders are activated within 24 hours of your request.