Free Proxy List Methodology and Coverage Limits

The Databay website consumes proxy records produced by an upstream checking service and publishes recent rows in HTML and machine-readable formats. The website code filters required country fields and uses a six-hour freshness window, with a narrower primary window for preferred rows. It exposes the record's last-check timestamp rather than claiming that every address is tested at the exact moment a visitor loads the page.

The upstream checker's complete acquisition list, probe infrastructure, raw request logs, geographic probe distribution, and source code are not part of this website repository. Therefore this page does not claim an independently reproducible count of probes, candidate sources, scan rate, or internal retry behavior.

The public API can return IP address, port, country and ISO code, protocol, SSL state, anonymity label, Google-passed flag, latency, uptime, and last-checked timestamp. These values are observations supplied by the checker and selected by the website; they are not certifications.

Country is a geolocation estimate. Protocol and SSL fields describe the observed test. Anonymity is a header-judge classification. Google-passed describes a previous probe result. Latency and uptime depend on the checker's route, time, endpoint, and history. Last checked is the timestamp attached to that record.

Databay describes the list as refreshed every 5 minutes. That is a rolling service target, not a guarantee that each visible address is rechecked exactly every 5 minutes. Use the per-record timestamp to judge a row, and expect addresses to disappear, change behavior, or fail between the recorded probe and your request.

A country page may have no current rows. Empty pages are labeled as availability pages and are not presented to search engines as live proxy datasets.

The list is available as server-rendered HTML, JSON, CSV, and plain text. API filters can select fields such as protocol, country, SSL, anonymity, Google result, speed, limit, and page. The file routes and API are subject to current server limits and can return an empty or partial result.

All formats are views of the same application data at request time, but requests made at different times can have different hashes because the dataset changes. Consumers should store retrieval time, parameters, status, content type, and hash.

Databay does not verify the identity, consent, security, logging, retention, intent, ownership, or legal status of each unknown public proxy operator. A working tunnel does not prove throughput, stability, safety, destination acceptance, or future behavior. A Google-passed result does not predict access to Google or another service from a different place or time.

The list does not test every destination, client, protocol feature, IPv6 path, browser leak, or threat scenario. Treat every endpoint as untrusted and unsuitable for credentials, sessions, personal data, private research, payments, or downloads.

Retrieve a record and then make one disposable request to a diagnostic endpoint you own or are authorized to use. Keep certificate validation enabled. Record the list retrieval time and hash, row timestamp, apparent source, destination, response status, elapsed time, and inspected headers.

Your result can differ from Databay's record because routing, endpoint behavior, address ownership, and proxy configuration change. Report the difference as a time- and route-specific observation, not proof that either measurement is universally correct.