20 IPs for 60 minutes on the country-mix package. No card required.
Start free trialA proxy login and password on top of the required IP whitelist — two-layer access that works from any machine on your network.
Proxy authentication is a challenge–response exchange. Over HTTP it looks like this: your client sends a request, the proxy answers with 407 Proxy Authentication Required, and the client retries with a Proxy-Authorization header carrying login:password in Base64. That's encoding, not encryption — on an unencrypted hop anyone in the path can read the credentials back out. If that hop matters in your setup, the TLS connection to the proxy closes it.
SOCKS5 does it differently: the credentials are negotiated inside the connection handshake (RFC 1929), before any application data flows. Either way, a SOCKS5 proxy with username and password gives you access that travels with the user, not the machine — unlike a whitelist rule, credentials aren't tied to your source address. That's why we issue them together with mandatory IP whitelisting, never instead of it: a leaked password is useless without a whitelisted IP, and a stranger behind your NAT can't get through without the credentials.
Buy a proxy server with a username and password when the whitelist alone is inconvenient: home internet with a changing IP, work from several locations, tools with mandatory login fields, shared team access. The login:password@ip:port format works everywhere — from curl to antidetect browsers. Specs are in the adjacent panel; pricing is in the calculator above.
Three access-control setups — and how they differ in security and convenience.
| No authenticationpublic access | IP whitelistingwhitelist | This page IP whitelisting + credentials |
|
|---|---|---|---|
| Who can use the proxy | Anyonethe proxy is open to the whole internet | Only requests from your IPs | Requests from approved source IPs with valid credentials |
| Security | Lowanyone who knows the proxy address can use it | Highaccess is restricted to approved source IPs | Highestboth the source IP and credentials are checked |
| Software setup | Proxy address only | Proxy address only | Proxy address, username, and password |
| If your IP is dynamic | No update required | Update the approved source IP in your Dashboard | Update the approved source IP in your Dashboard |
| Where it's available | Public proxy lists — we don't offer these | Every PapaProxy.net plan | Every PapaProxy.net plan |
| Not recommended for real work | Buy now | Buy now |
At PapaProxy.net, IP whitelisting is required for every proxy. Username/password authentication is optional and adds a second access-control layer.
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 | |
|---|---|---|---|---|
| 45.80.111.172 | DE | 80 | HTTP | |
| 45.80.111.126 | DE | 80 | HTTP | |
| 45.80.111.34 | DE | 80 | HTTP | |
| 45.80.111.167 | DE | 80 | HTTP | |
| 45.80.111.159 | DE | 80 | HTTP | |
| 45.80.111.58 | DE | 80 | HTTP | |
| 45.80.111.102 | DE | 80 | HTTP | |
| 45.80.111.51 | DE | 80 | HTTP | |
| 45.80.111.128 | DE | 80 | HTTP | |
| 45.80.111.118 | DE | 80 | HTTP |
A few service metrics—and feedback from our customers.
Хорошая скорость, доходит до 1Гбит/с. Прокси поддерживают многопоток. На один адрес по 1 млн одновременных запросов выдерживают. Пытался положить сервер – не выходит. Качественные прокси, рекомендую.
For the third time I renewed my subscription, there were no crashes. Not a single account has crashed, which means that the proxy works very well. I advise to use them.
I have no complaints about the service. I have bought more than a dozen proxies, all work, the speed is acceptable. In 3 months of use nothing flies off, speeds do not drop. Admins respect. If you are looking for a reliable solution, consider their new fast private socks proxy service provider for top-tier performance and reliability.
The main thing is to check their proxy list and make sure it is up-to-date and in good condition.
Can't find your answer? Message us in live chat — real humans reply.
Not instead — only together: IP whitelisting is required on every plan. A changing IP does not block you: update your whitelist in the Dashboard or via the API. Your ISP assigns a new address — one API call restores access; you can automate that with a script on your router or server. More on using our proxies with a dynamic IP.
Because an IP is a network address, not a personal key. Every device behind your home router looks the same to the proxy, as do all colleagues behind office NAT. A password narrows access: not «anyone on your IP,» but whoever knows the credentials. It also helps if your ISP reassigns your old IP to another customer while your whitelist entry still points at it.
Check the special characters first. In the inline login:password@ip:port format, the characters @, :, and % are separators — a password containing @ splits the URL in the wrong place, and the proxy receives garbage instead of your credentials. Two fixes: percent-encode the character (@ becomes %40), or skip inline entirely and pass credentials through a dedicated option — curl has --proxy-user, most libraries have separate username/password fields that take the raw string. On our plans there's a second thing to verify: credentials work alongside the whitelist, so if your source IP isn't added in the Dashboard, no password will get you through.
Whitelist every work location — up to five slots included — and share the proxy server login through a password manager, not as plain text in a messaging app. A proxy with username/password authentication does not tell who connected, so split package IPs between people upfront: two people on one IP hitting the same target site is an easy path to bans.
Not in source code. Store the username and password in environment variables or a .env file listed in .gitignore; the script should only read them at runtime. Leaked proxy credentials in a public repository are common — bots scan GitHub faster than most teams notice an accidental push. Even leaked credentials will not work without a whitelisted source IP on our end — but you should not rely on testing 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.