PYPROXY

What Is PYPROXY?

If you need to appear online from a specific country (or a rotating set of countries) without running a full VPN client, you’re typically looking for a proxy network you can plug into scripts, browsers, or automation tools. PYPROXY is built for that exact use case: paid proxy access (residential, ISP, mobile, and datacenter pools) delivered through standard proxy protocols instead of a consumer “VPN app.” (pyproxy.com)

In practice, this is aimed at people doing web testing, data collection, account management, and geo-specific access where you need a lot of exit IPs and control over rotation/stickiness. PYPROXY’s documentation emphasizes buying small traffic allowances to test against your real targets before scaling up, which is a realistic stance for proxy work (sites block proxies all the time). (pyproxy.com)

What makes it distinctive (for better and worse) is the “proxy-first” approach: billing is primarily per-GB for rotating products, traffic doesn’t expire, and delivery is tied to crypto payments with instant provisioning. It also exposes multiple access methods (username/password and IP whitelisting) and is explicit about technical limitations like SOCKS5 being TCP-only on their gateway. (pyproxy.com)

PYPROXY Features and Performance

The core capability is a global proxy network with country selection (our database lists coverage in 195 countries). You connect to PYPROXY like a typical proxy provider—your apps use HTTP, HTTPS, or SOCKS5 depending on the pool/product you purchased and the gateway port you connect to. (pyproxy.com)

Protocols and endpoints (what’s actually documented): PYPROXY’s FAQ states that rotating residential supports HTTP and HTTPS on port 1111 and SOCKS5 on port 2222, using the same credentials on both. It also states SOCKS5 is TCP-only with no UDP association, which matters if your workload depends on UDP (many VPN protocols do; some apps try UDP-based behaviors). (pyproxy.com)

There are two authentication styles:

• Username/password on ports 1111 (HTTP/S) and 2222 (SOCKS5). (pyproxy.com)
• IP whitelisting for fixed-server environments, using gw.pyproxy.com:8081 for HTTP/S with no credentials sent. PYPROXY explicitly notes whitelisting does not (yet) work with SOCKS5 on their service.

Rotation and session behavior: PYPROXY distinguishes “rotating” IPs (change per request) from “sticky sessions” that hold an IP for up to 30 minutes. If you’re doing logins or workflows that break when the IP changes mid-session, this sticky option is the difference between “works” and “doesn’t.” (pyproxy.com)

Performance expectations: PYPROXY does not publish hard guarantees for speed/latency or uptime. In its Terms, it warns that it does not promise reachability to any specific website, that proxy pools are shared, and that targets can block proxies at any time. Translation: you should treat performance as target-dependent, not provider-dependent marketing numbers. (pyproxy.com)

“DNS & Private Browsing” reality check: Despite the label you provided (“DNS & Private Browsing”), PYPROXY is a proxy service. The official docs focus on proxy gateways, ports, authentication, rotation, and billing—not DNS features like DoH/ODoH or a “private browser” mode. If your threat model is DNS privacy or hiding traffic from your ISP, a proxy can help in some situations, but it’s not a drop-in substitute for a VPN + encrypted DNS setup—and PYPROXY itself explicitly notes SOCKS5 is TCP-only and “plain DNS” won’t work over it. (pyproxy.com)

Pricing and Plans

PYPROXY is paid (no free tier is advertised in the official FAQ), and the pricing is primarily usage-based for rotating products.

From PYPROXY’s published pricing table (FAQ), starting prices are:

• Rotating Residential: $0.67/GB (per-GB, non-expiring) (pyproxy.com)
• Rotating ISP: $1.00/GB (pyproxy.com)
• Mobile 4G/5G: $2.38/GB (pyproxy.com)
• Datacenter IPv4: $0.70/GB (pyproxy.com)
• Datacenter IPv6: $0.19/GB (pyproxy.com)
• SOCKS5 per-IP: $0.045/IP (pyproxy.com)

Billing mechanics are also spelled out:

• Rotating products are billed per gigabyte, with no per-thread or per-IP charges, and traffic never expires. (pyproxy.com)
• “SOCKS5 per-IP and static products” are billed per IP or per month (structure described, but not all tier details are in the FAQ excerpt). (pyproxy.com)
• The Terms describe purchases as prepaid allowances, not auto-renewing subscriptions (“Nothing renews automatically”). (pyproxy.com)

Payments: PYPROXY states payment is currently cryptocurrency (USDT, BTC, ETH, LTC “and more”), and says card payments are “on the way.” (pyproxy.com)

Refund window: PYPROXY’s Refund Policy is unusually explicit for a proxy provider: it offers a refund of unused traffic within 7 days in certain cases (including “changed your mind” with no consumption, or service failure they can’t fix). Used traffic is not refunded, and accounts closed for Acceptable Use violations get no refund. Refunds are paid via a new crypto transfer (network fees deducted) and are denominated in the crypto asset you paid with.

Privacy and Security Assessment

Jurisdiction: PYPROXY is operated by “HONGKONG LINGYUN NETWORK MDT INFOTECH LIMITED,” and the Terms list a Hong Kong address. That aligns with your database note (Hong Kong jurisdiction). Jurisdiction matters because any provider can be compelled to produce data it has—so the key question is what they actually retain. (pyproxy.com)

Logging claims (what they say): PYPROXY’s Privacy Policy states they do not log the websites you visit through the proxies, the content of requests, or the responses you receive. It also says the network meters bytes transferred, but does not keep a record of “where you moved them.” It claims no advertising trackers/analytics pixels and says the only cookie used is a session cookie.

What they do collect: The same Privacy Policy lists account and operational data: email address, password hash (PBKDF2-SHA256 + salt), session token plus IP address/user-agent that created it, order details (volume, price, currency, promo code, payment status/timestamps, payment reference), and remaining traffic plan/balance. That’s normal for running a paid service, but it’s still personal/metadata you should assume exists.

Third parties: PYPROXY says the payment processor gets an order reference and amount (and that your crypto wallet address is visible to the processor, not to PYPROXY), and an “upstream network provider” receives a request to issue a traffic plan with an opaque label (no email). If you’re trying to minimize data sharing, that’s at least a clear disclosure.

Audits / open source / independent verification: PYPROXY does not present an independent no-logs audit in the documents reviewed here, and the service itself is not presented as open-source. (There is an unrelated GitHub project named “pyproxy” that is a Python proxy server, but that’s not evidence that PYPROXY’s commercial network is open-source or audited.)

Operational honesty: The Terms explicitly warn there’s no guaranteed uptime figure/service credits, and that you should test with a small allowance because blocks happen and they don’t promise any given site will work. That’s not “privacy,” but it’s relevant security hygiene: proxy networks are adversarial environments. (pyproxy.com)

Strengths and Limitations

Strengths

• Clear protocol/port documentation (1111 for HTTP/S, 2222 for SOCKS5) and explicit TCP-only SOCKS5 limitations. (pyproxy.com)
• Usage-based billing on rotating products with non-expiring traffic, which is often more practical than monthly “use it or lose it” bandwidth. (pyproxy.com)
• IP whitelisting option for servers that need passwordless proxy auth (useful in production).
• Straightforward refund policy (7 days; unused traffic; defined “does not work” criteria).

Limitations

• Not a VPN. SOCKS5 is TCP-only and PYPROXY explicitly notes UDP-based use cases (including “plain DNS”) won’t work through that SOCKS5 channel. If you need full-tunnel VPN behavior, this isn’t it. (pyproxy.com)
• Crypto-only payments (currently). If your organization needs card/invoice workflows, “card payments are on the way” isn’t the same as supported today. (pyproxy.com)
• No published uptime/SLA and no promise that any particular site will allow access; you have to test targets yourself. (pyproxy.com)
• No independent audit claim for logging/privacy in the materials reviewed; you’re relying on policy statements.

Who Should Use PYPROXY?

Good fit

1. Developers and automation users who need HTTP(S)/SOCKS5 proxy endpoints for scripts, bots, QA, or multi-region testing, and prefer paying by traffic instead of fixed monthly bundles. (pyproxy.com)

2. Teams that need “sticky” sessions (up to 30 minutes) for workflows where the IP must remain stable across multiple requests (login flows, carts, account management). (pyproxy.com)

3. Server-based workloads where IP whitelisting is convenient (no credentials embedded in config files), as long as HTTP/S is sufficient for that workflow.

Not a great fit

1. Anyone who needs a consumer VPN experience (apps, full-device tunneling, UDP support, “set and forget”). PYPROXY is a proxy service with TCP-only SOCKS5 on its gateway, and it’s explicit that some UDP-dependent use cases won’t work. (pyproxy.com)

2. Users who can’t or won’t pay with cryptocurrency, since PYPROXY states crypto is the current method and cards are not yet available. (pyproxy.com)

3. Buyers who require audited no-logs assurances for compliance. PYPROXY publishes a privacy policy describing minimal logging, but an external audit is not presented in the official materials reviewed here.