4,362 live HTTP, HTTPS, SOCKS4 and SOCKS5 proxy endpoints come from the same verification snapshot. Countries represented: 126.
Latest verification snapshot
Protocol availability
Rechecked every 5 minutes
4,362verified endpoints126 countries represented
HTTP
2,67461%
HTTPS
2,52258%
SOCKS4
1,08125%
SOCKS5
60714%
Protocol capabilities can overlap on the same verified endpoint.
Live proxy list
Live free proxy servers
Looking for a fast free proxy list? Click Latency in the table to sort recent measurements from low to high, or use the free proxy list API with speed=fast to download the measured fast subset. Results are recent probes, not a speed guarantee for every destination.
Keep using the public list for configuration practice and low-risk, one-off checks. Consider a managed pool when a permitted workload needs authenticated gateways, an orderable bandwidth allowance, location controls or a specific network origin. Public endpoints can disappear between checks and should never carry secrets.
The free utility stays open
No email or payment is required for the table, downloads or API. Choosing paid below does not unlock or change the free dataset.
Rate snapshot: . Prices and checkout are removed automatically when this catalogue snapshot expires.
Understanding proxies
What is a free proxy server?
How an IP address and port route a request, what the destination can observe, and what a public proxy cannot protect.
A free proxy server sits between your client and a destination. You connect to its IP address and port, and it forwards the request from its own network address. The destination usually sees the proxy's IP for that request instead of your direct connection.
A proxy does not make you anonymous, change every location signal, encrypt every protocol, or authorize access. Public endpoints can be unstable, and their operators may inspect or log traffic. Never send credentials, payment details, or other sensitive data through an operator you do not trust.
Your Device
Proxy Server
Internet
The destination sees the proxy’s network IP for that request. Headers and other signals can still identify you.
Protocols
HTTP, HTTPS, SOCKS4 and SOCKS5 proxy protocols
Choose a protocol based on the traffic your client sends, its DNS needs, and whether it must create an HTTPS tunnel.
Protocol
Layer
Encryption
Best For
HTTP
Application
None
Plain HTTP requests and testing
HTTPS
Application
TLS tunnel
HTTPS requests with client-side certificate checks
SOCKS4
Transport
None
Basic TCP forwarding and legacy clients
SOCKS5
Transport
None by default
TCP, optional UDP, authentication, remote DNS
Swipe
HTTP proxies
Forward plain HTTP requests at the application layer. They are simple to configure, but the proxy can read unencrypted traffic, so never send sensitive data.
HTTPS proxies
Use the HTTP CONNECT method to relay a TLS connection. Your client must still validate the destination certificate. A public operator remains unsuitable for sensitive activity.
SOCKS4 proxies
Relay TCP with a small handshake but no built-in authentication or UDP support. SOCKS4a adds remote hostname resolution for clients that implement it.
SOCKS5 proxies
Can relay TCP and, when both sides support it, UDP. SOCKS5 supports authentication and remote DNS, but it does not encrypt application traffic by itself.
These labels summarize what Databay's latest header probe observed. They do not measure operator trust, encryption, DNS leaks, browser fingerprinting, cookies, or account identity.
Candidates are collected from public proxy sources and tested before publication. An IP address and port appear only after the checker records a successful connection.
Probe pipeline
Candidates are checked on a rolling five-minute schedule. The checker attempts a TCP connection, runs the applicable HTTP and HTTPS requests, records the successful round-trip time, and observes selected response headers.
What the columns mean
Latency is the round-trip time of the latest successful checker request. Fast is below 500 ms, Medium is 500 to 1,499 ms, and Slow is 1,500 ms or more.
Uptime is the percentage of recorded checks that succeeded over the lifetime of the IP address and port pair.
Reachability probe records that the upstream checker received its expected response for that route and time. It does not authorize automated queries, certify reputation, or predict a later response.
HTTPS states
HTTPS support is reported in three states:
Strict: the checker created an HTTPS tunnel and validated the destination certificate chain.
Loose: the HTTPS request succeeded only when certificate validation was disabled.
None: the checker did not complete an HTTPS tunnel through this endpoint.
Expiry policy
The pool includes only endpoints with a successful check less than six hours old. The last-checked value remains visible so you can judge freshness, and rows at or beyond the cutoff are excluded. If the pool observation is stale or unavailable, current inventory is withheld.
The Databay column describes this page and its current server-rendered counts. Other services vary, so their documentation and terms remain the source of truth.
Use the stable worldwide, protocol, or country hotlink when a script needs one IP:PORT endpoint per line instead of structured metadata.
Exact output contract
The first two lines begin with # and describe the feed. Every remaining non-empty line is oneIP:PORT endpoint. The file is refreshed on the published rolling schedule, but an endpoint can fail or change after its latest successful check.
Choose TXT only when the fields fit
TXT is convenient for line-oriented tools. Choose CSV or JSON when you also need protocol flags, country, latency, uptime, anonymity, HTTPS state, or the last-check value. Downloading a recent public endpoint is not a security review or a promise of future availability.
Protocol files are available at /http.txt, /https.txt, /socks4.txt, and/socks5.txt below /free-proxy-list/. Country hotlinks use the canonical country slug, such as /free-proxy-list/united-states-of-america.txt.
# Save the current worldwide list
curl -fsS "https://databay.com/free-proxy-list.txt" -o proxies.txt
# Ignore the two comment lines when piping endpoints
curl -fsS "https://databay.com/free-proxy-list/socks5.txt" | grep -v '^#'
from urllib.request import urlopen
url = "https://databay.com/free-proxy-list.txt"
lines = urlopen(url, timeout=15).read().decode("utf-8").splitlines()
proxies = [line for line in lines if line and not line.startswith("#")]
print(f"Loaded {len(proxies)} IP:PORT endpoints")
Fetch the live proxy server list as JSON, CSV or TXT. No key or signup. The public API is uncapped at the application layer, with responses cached for 15 seconds.
Base URLGET https://databay.com/api/v1/proxy-list
# Get all proxies (JSON)
curl "https://databay.com/api/v1/proxy-list"
# Filter by protocol and country
curl "https://databay.com/api/v1/proxy-list?protocol=socks5&country=US"
# Get US SOCKS5 proxies as CSV
curl "https://databay.com/api/v1/proxy-list?protocol=socks5&country=US&format=csv"
# Get the low-latency subset as plain text
curl "https://databay.com/api/v1/proxy-list?speed=fast&format=txt"
import requests
# Fetch fast SOCKS5 proxies in Germany
resp = requests.get("https://databay.com/api/v1/proxy-list",
params={"protocol": "socks5", "country": "DE", "speed": "fast"})
data = resp.json()
for proxy in data["data"]:
print(f"{proxy['ip']}:{proxy['port']} - {proxy['latency']}ms")
# Permanent plain-text files - one IP:PORT per line, refreshed every 5 minutes
https://databay.com/free-proxy-list.txt
https://databay.com/free-proxy-list/http.txt
https://databay.com/free-proxy-list/https.txt
https://databay.com/free-proxy-list/socks4.txt
https://databay.com/free-proxy-list/socks5.txt
# Full-list CSV and JSON files
https://databay.com/free-proxy-list.csv
https://databay.com/free-proxy-list.json
# Per-country (canonical country slug)
https://databay.com/free-proxy-list/<country>.txt # e.g. /united-states-of-america.txt
Query parameters
Parameter
Type
Default
Description
protocol
string
all
http, https, socks4, socks5
country
string
all
ISO 2-letter code (US, DE, etc.)
anonymity
string
all
elite, anonymous, transparent
ssl
string
all
strict (valid cert), loose (any HTTPS)
google
bool
all
true = passed the latest limited reachability probe; not an access guarantee
Do not assume a public proxy is safe. Its operator may inspect or log traffic, and a successful Databay check is not a security review. Use the list only for non-sensitive testing, never for credentials, personal data, payments, or private accounts.
What is the difference between a free proxy list and a free web proxy?
A proxy list provides IP addresses and ports that you configure. A web proxy is a website where you paste a URL. Databay provides a server list, not a web proxy.
How often is the list updated?
Candidates are checked on a rolling five-minute schedule. Use Last Checked for a specific result. Only endpoints with a successful check less than six hours old are published; older rows are excluded.
What is the difference between HTTP, HTTPS, SOCKS4 and SOCKS5 proxies?
HTTP forwards plain web requests, while HTTPS-capable HTTP proxies relay TLS with CONNECT. SOCKS4 relays TCP. SOCKS5 can add authentication, remote DNS, and optional UDP support.
What do elite, anonymous and transparent mean?
These are header observations, not security ratings. Elite exposed neither the tested client IP nor common proxy markers; anonymous exposed a proxy marker but not the tested IP; transparent exposed the tested IP.
How do I get a free proxy from this list?
Choose a recently checked row, copy its IP address and port, and select the matching protocol in your client. For bulk use, download TXT, CSV or JSON, or call the free API. No signup is required.
Is there a free API?
Yes. The /api/v1/proxy-list endpoint returns the live list as JSON, CSV or TXT with filters for protocol, country, SSL, Google-pass, speed and anonymity. No key required.
Can I filter by country or protocol?
Yes. Use the country pages, the protocol pages (HTTP, HTTPS, SOCKS4, SOCKS5) and the anonymity pages (elite, anonymous, transparent), or the API query parameters.
Why do some proxies stop working quickly?
Public endpoints can become overloaded, change configuration, or go offline without notice. A result only describes the latest successful check, so expect failures and use timeouts and retries for testing.
Do these proxies support HTTPS?
Some do. Strict means the checker completed an HTTPS request with certificate validation; Loose required validation to be disabled; None means no HTTPS tunnel completed. Do not send sensitive data through a public operator.
What does "Google passed" mean?
It records that the upstream checker received its expected Google probe response for that route and time. It is not a reputation, safety, or future-access guarantee.
Should I use free proxies for scraping or automation?
Use public proxies only for permitted, non-sensitive experiments. They are too unstable for dependable automation and do not override terms, robots controls, authentication, or rate limits.
From the blog
Latest from the blog
Setup guides, benchmarks, and research notes on proxies and web data collection.
