Ultra-Fast Proxy Fetcher & Tester

Fetch, validate, rank, and save public HTTP, SOCKS4, and SOCKS5 proxy endpoints with one Python script. The engine uses bounded asynchronous concurrency, strict public-address filtering, and an end-to-end HTTPS connectivity check.

This project is intended for authorized network testing, software development, and research. Public proxies are untrusted. Never send credentials, personal information, proprietary data, or other sensitive traffic through an endpoint produced by this tool.

Version 2.0.0 is the current verified release. Download the standalone runtime and integrity files from the release page.

Why this version is different

• Fetches concurrently from 52 curated HTTPS sources validated on 2026-08-12.
• Rejects private, loopback, link-local, multicast, reserved, malformed, and invalid-port entries before attempting a proxy connection.
• Validates HTTP CONNECT, SOCKS4, and SOCKS5 transports against a fixed HTTPS endpoint that must return exactly 204.
• Blocks unsafe source URLs and redirects, verifies source TLS, checks DNS destinations, and caps decompressed response sizes.
• Uses bounded worker pools, source concurrency, timeouts, and a default 5,000-candidate safety cap.
• Caps every source at 5 MiB and 10,000 unique endpoints to constrain hostile or malformed feeds.
• Does not display third-party proxy addresses in live progress output.
• Atomically invalidates stale output before testing and replaces it with the completed report, including when no proxies work.
• Keeps all application logic in proxy_fetcher_ultimate.py.

Requirements

• Python 3.10 or newer
• Internet access to the configured source hosts and HTTPS connectivity endpoint

Installation

git clone https://github.com/fusiontechstrategies/Ultra-Fast-Proxy-Fetcher-Tester.git
cd Ultra-Fast-Proxy-Fetcher-Tester
python -m venv .venv

Activate the environment on Windows:

.venv\Scripts\Activate.ps1

Activate it on Linux or macOS:

source .venv/bin/activate

Install the runtime dependencies:

python -m pip install --upgrade pip
python -m pip install -r requirements.txt

Usage

Run with safe defaults:

python proxy_fetcher_ultimate.py

Fetch and validate source data without testing or saving proxy endpoints:

python proxy_fetcher_ultimate.py --fetch-only

Test a smaller HTTP-only sample:

python proxy_fetcher_ultimate.py --protocol http --max-candidates 500 --concurrent 50

Choose a different output file and hide live progress:

python proxy_fetcher_ultimate.py --output results/proxies.txt --quiet

Show every option and its enforced bounds:

python proxy_fetcher_ultimate.py --help

Show the stable product version:

python proxy_fetcher_ultimate.py --version

Important defaults

Actual throughput depends on network conditions, operating-system limits, candidate quality, protocol mix, and timeout settings. The project deliberately makes no fixed checks-per-second promise.

Output

Working endpoints are sorted by measured response time and grouped into speed categories. The following addresses are documentation-only examples and are never shipped as a usable proxy list:

# LIGHTNING FAST (under 200ms)
http://192.0.2.10:8080              # 142.18ms

# VERY FAST (200-499ms)
socks5://198.51.100.20:1080         # 318.42ms

Generated proxy files are excluded by .gitignore. Treat them as transient operational data.

Exit codes

Security model and limitations

• The fixed HTTPS 204 check validates connectivity and TLS tunneling. It does not prove anonymity, trustworthiness, geographic location, uptime, or ownership.
• A proxy can become malicious or unavailable immediately after a successful test.
• Third-party source availability and content can change without notice.
• Source entries are data from independent projects. This repository does not redistribute a current proxy snapshot.
• The application ignores system proxy environment variables for source retrieval and test traffic.
• Adding custom target URLs is intentionally unsupported to reduce misuse and accidental traffic against third parties.

Read SECURITY.md for vulnerability reporting and RESPONSIBLE_USE.md before operating the tool.

Release integrity

The v2.0.1 release process is designed to contain exactly seven files:

1. an exact standalone copy of proxy_fetcher_ultimate.py
2. a deterministic source and documentation ZIP
3. a verified Python wheel
4. a verified Python source archive
5. an SPDX 2.3 direct-dependency SBOM
6. SHA256SUMS.txt
7. commit-bound release-evidence.json

The builder uses a fixed file allowlist, canonical ZIP order, timestamps, permissions, and metadata. It rejects mismatched versions, tags, dependencies, source files, commits, or output sets. GitHub Actions builds the assets twice, compares every byte, exercises the exact standalone runtime without network access, and attests every asset before creating a draft. The workflow cannot publish the draft and does not publish to a package registry.

See RELEASING.md for the exact contract and TESTING.md for offline, live, and release validation boundaries.

Development

Install the development checks:

python -m pip install -r requirements-dev.txt

Run the same offline checks used by GitHub Actions:

python -m pip check
python -m ruff check .
python -m ruff format --check .
python -m unittest discover -s tests -v
python -m mypy proxy_fetcher_ultimate.py
python -m bandit -q -r proxy_fetcher_ultimate.py
python -m pip_audit -r requirements.txt
python -m pip_audit -r requirements-dev.txt

See CONTRIBUTING.md for source-review and pull-request requirements.

License

Released under the MIT License.