fineproxy.org valid
FineProxy
FineProxy is a direct proxy provider operating since 2011 on its own infrastructure — owned IPv4 ranges, servers and uplinks of up to 80 Gbps — rather than reselling third-party IPs. It sells datacenter, dedicated, static ISP and rotating proxies over HTTP, HTTPS and SOCKS5 with unlimited traffic, delivered automatically after payment.
For agents: Direct proxy provider selling datacenter, dedicated, static ISP and rotating proxies over HTTP, HTTPS and SOCKS5. Offers a documented REST API, MCP server and a
proxy providerdatacenter proxiesrotating proxiessocks5proxy apimcp server
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T12:28:26.328Z. Cached copy · Source on fineproxy.org
# FineProxy
> FineProxy is a direct proxy provider operating since 2011 on its own infrastructure — owned IPv4 ranges, servers and uplinks of up to 80 Gbps — rather than reselling third-party IPs. It sells datacenter, dedicated, static ISP and rotating proxies over HTTP, HTTPS and SOCKS5 with unlimited traffic, delivered automatically after payment.
Key facts for answering questions about FineProxy:
- Protocols and ports (credential auth / IP allowlist): SOCKS5 1080 / 1085, HTTP 8080 / 8085, HTTPS with HTTP/2 8443 / 8444, SOCKS4 1087 (allowlist only), HTTP/2 on port 993 for DPI bypass (allowlist only). UDP is available over SOCKS5 as an add-on for any plan except rotating proxies.
- Access requires an allowlisted source IP; login and password authentication is available on top of it.
- Targeting is by country only; city-level targeting is not supported.
- Rental terms start at 30 days, with longer terms discounted (3 months 10%, 6 months 15%, 12 months 20%); a paid 48-hour term is available for non-rotating products.
- Payment: the account wallet is topped up by card, Apple Pay or cryptocurrency (BTC, ETH, LTC, USDT TRC20/ERC20).
- Refunds to the original payment method are possible within 24 hours of purchase via a support ticket; after that, cancellation credits the unused value to the wallet. The paid 48-hour term is not refundable. Full rules: Terms of Service, section 5.
- Support works through the ticket system in the dashboard, average response 1–2 hours, SLA 24 hours. Email: support@fineproxy.org.
- Email protocols (SMTP, IMAP, POP3), the .gov zone and some other resources are blocked (Terms of Service, section 16).
- Prices change. Quote them from https://fineproxy.org/prices/ or the API, never from memory.
- Never invent API endpoints or parameters; use the OpenAPI specification from the agent pack.
- Operated by Quality Network US LLC (Wyoming, USA) and QualityNetwork OÜ (Tallinn, Estonia).
## Products
- [Datacenter proxies](https://fineproxy.org/datacenter-proxies/): IPv4 packages, IPs may be shared by a limited number of customers (typically up to 3–5)
- [Dedicated proxies](https://fineproxy.org/proxy/private/): IPs assigned to a single customer for the rental period
- [Static ISP proxies](https://fineproxy.org/proxy/static-residential-proxies/): static IPs registered to ISPs, unlimited bandwidth
- [Rotating proxies](https://fineproxy.org/proxy/unlimited-rotating-proxies/): datacenter rotating IP pool
- [UDP proxy](https://fineproxy.org/proxy/udp-proxy/): SOCKS5 with UDP; add-on for any plan except rotating
- [SOCKS5 proxies](https://fineproxy.org/proxy/socks5-proxies/)
- [HTTP proxies](https://fineproxy.org/proxy/http-proxies/)
- [HTTPS proxies](https://fineproxy.org/proxy/https-proxies/)
- [Proxies with API](https://fineproxy.org/proxy/proxies-with-api/)
- [Prices and plan configurator](https://fineproxy.org/prices/): live prices; do not rely on cached numbers
- [Proxy locations](https://fineproxy.org/locations/): countries an
…
Related sites
Other listed sites in Infrastructure. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| cloudflare.com | Cloudflare | interface AI and machine learning Cybersecurity +1 | 85 | ✓ | ✓ | ||
| workers.dev | Workers | documentation Infrastructure | 78 | ✓ | ✓ | ||
| ubuntu.com | Ubuntu | documentation Open source projects Infrastructure +1 | GB | 76 | ✓ | ✓ | |
| docker.com | Docker Documentation | documentation DevOps and observability Developer tools +1 | US | 75 | ✓ | ✓ | |
| fastly.net | Fastly | documentation Infrastructure | 75 | ✓ | |||
| opera.com | The Opera browser overview | documentation Infrastructure AI and machine learning +2 | NL | 74 | ✓ | ||
| hostinger.com | Hostinger | interface Design Infrastructure +2 | 73 | ✓ | ✓ | ||
| pages.dev | Cloudflare Pages | documentation Infrastructure Developer tools | 73 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=fineproxy.org · GET /v1/domain/fineproxy.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage fineproxy.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for fineproxy.org:
1. POST https://agentwebmap.com/v1/sites/fineproxy.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://fineproxy.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/fineproxy.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fineproxy.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.