# ALIILAPRO/Proxy: An Hourly Updating Proxy List You Can Pull from GitHub

> A minimal GitHub repository that publishes fresh HTTP, SOCKS4, and SOCKS5 proxy addresses every hour, aimed at developers who need a quick source of proxies without running their own collector.

**ALIILAPRO/Proxy** — Get new and fast proxy list every hour.

- Repository: https://github.com/ALIILAPRO/Proxy
- Website: http://aliilapro.ir/Proxy/
- Stars: 199 · Forks: 20
- Language: CSS
- License: MIT
- Published: 2026-08-22 · Updated: 2026-08-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/aliilapro-proxy

## What This Repository Actually Provides

ALIILAPRO/Proxy is a GitHub repository that hosts three plain text files: http.txt, socks4.txt, and socks5.txt. Each file contains a list of proxy addresses, one per line, in the standard IP:port format. The README states that the lists are updated every hour, giving you a fresh set of proxies without having to scrape websites or run your own checker. The intended audience is clear: developers or hobbyists who need a quick supply of proxies for tasks like web scraping, geolocation testing, or load balancing experiments. The repository does not provide any code, API, or configuration; it is purely a data source. The primary language listed is CSS, which is odd because there is no CSS in the README or the described files. That likely reflects a default GitHub classification, not the actual content. The project is licensed under MIT, so you can reuse the lists with minimal restrictions, though the readme includes a note that the author is not responsible for the proxies.

## How the Hourly Update Mechanism Works

The README does not explain the update mechanism in detail. It simply says 'Get new and fast proxy list every hour.' From the repository structure, you can infer that a script or automated process runs on the maintainer's side, collects proxies from public internet sources, filters them for speed, and then commits the updated files to the main branch. The raw.githubusercontent.com URLs are the only way to access the data; there is no API endpoint or versioning. This means the update is not a service you can subscribe to; you must poll the raw files yourself if you want the latest list. The documentation gives no information about how the proxies are verified for speed or anonymity. The term 'fast' in the description is a claim made by the maintainer, but there is no benchmark data in the repository to support it. For a user, the practical mechanism is simple: fetch the file, parse the lines, and use them. The hourly cadence is a promise, not a guarantee, and the actual frequency depends on the maintainer's schedule.

## Getting the Proxy Lists: Commands and URLs

To use the lists, you do not need to clone the repository. The README provides direct raw URLs for each proxy type. For HTTP proxies, use: https://raw.githubusercontent.com/ALIILAPRO/Proxy/main/http.txt. For SOCKS4, use: https://raw.githubusercontent.com/ALIILAPRO/Proxy/main/socks4.txt. For SOCKS5, use: https://raw.githubusercontent.com/ALIILAPRO/Proxy/main/socks5.txt. A typical command to download the HTTP list on Linux or macOS is: curl -O https://raw.githubusercontent.com/ALIILAPRO/Proxy/main/http.txt. On Windows, you could use PowerShell's Invoke-WebRequest. Once downloaded, the file is a plain text file with one proxy per line, so you can read it with any scripting language. For example, in Python, you might do: with open('http.txt') as f: proxies = [line.strip() for line in f if line.strip()]. There is no authentication, no rate limiting mentioned, and no setup required. The raw URLs work directly from a browser or a script. This simplicity is the main appeal of the repository.

## Limitations and Failure Modes

The biggest limitation is reliability. The README explicitly disclaims responsibility, noting that the proxies are collected from internet sources and only displayed for easy access. That means the lists can contain dead proxies, malicious proxies, or proxies that are slow despite the 'fast' label. There is no uptime guarantee, no SLA, and no way to report a broken proxy. The hourly update is not a contract; if the maintainer stops pushing commits, the files become stale. Another failure mode is the lack of metadata. You get an IP and port, but no information about protocol version, anonymity level, or geographic location. For HTTP proxies, you do not know if they support CONNECT for HTTPS traffic. For SOCKS5, you do not know if they support authentication or UDP. This makes the list unsuitable for production use where you need predictable behavior. The repository is also a single point of failure: if GitHub is down or the repository is taken down, the data disappears. There is no mirror or backup mentioned.

## The Right Tool for Some, Wrong for Others

This repository is a good fit for quick experiments, such as testing a scraper against a rotating set of IPs, or for development environments where a few dead proxies are acceptable. It is a poor fit for any application that requires stable, authenticated, or geo-specific proxies. If you need that, you should look at commercial proxy services that offer APIs, uptime guarantees, and customer support. The difference in approach is fundamental: ALIILAPRO/Proxy is a free, community-sourced list with no quality control, while commercial services run their own infrastructure and verify proxies continuously. Another alternative is to run your own proxy checker, using tools like ProxyBroker or Scrapy with middleware, but that requires more setup and maintenance. The repository's value is its simplicity and zero cost, but that comes at the expense of control and reliability. For a quick test, it is fine; for a business dependency, it is not.

## Maintenance and License Implications

The maintenance cost for a user is low. You just download the files periodically. However, you need to write your own logic to fetch, parse, and validate the proxies. The repository itself has no issue tracker visible in the README, and there are no recent releases, so you cannot rely on versioned updates. The last push date is unknown, which is a warning sign: you should check the commit history on GitHub before using it. The MIT license means you can use, copy, modify, and distribute the lists, even for commercial purposes, as long as you include the original copyright notice. This is permissive, but it does not protect you from legal issues related to using proxies for activities that violate website terms of service. The license also means the maintainer gives no warranty, which aligns with the disclaimer in the README. In short, you get the data, but you bear all the risk.

## Conclusion

Adopt ALIILAPRO/Proxy if you need a quick, free, and regularly refreshed set of proxy addresses for testing, scraping, or routing experiments, and you are comfortable with the fact that the proxies are collected from public sources with no guarantee of reliability or safety. Do not use it for production traffic, sensitive data, or anything requiring consistent uptime. Before relying on it, verify the freshness of the files by checking the commit history on GitHub, test a sample of proxies for latency and anonymity, and review the MIT license to understand your rights and obligations. The repository is a convenience, not a service, and its value depends entirely on the goodwill of the maintainer to keep pushing updates.

## FAQ

### What does the ALIILAPRO/Proxy repository actually provide?

Three plain text files, one each for HTTP, SOCKS4 and SOCKS5, served as raw files from the default branch, plus a static page in front of them. The page says the addresses are refreshed every hour.

### Are the proxies in ALIILAPRO/Proxy tested or vetted?

The project states that the list is collected from proxies available on the Internet, that the addresses are only displayed for easy access, and that the author is not responsible for proxies. No test results are published.

### Can I pin a specific version of the ALIILAPRO/Proxy list?

No. All three raw URLs point at the main branch and the repository has no GitHub releases, so a fetch always returns whatever is currently committed. Record the commit yourself if you need to reproduce what you got.

### What line format does the ALIILAPRO/Proxy list use?

The page does not state one. It gives no schema, no separator, no credential format and no count of entries, so read a line from the file before pointing a client at it.

## Sources

- [Official documentation](http://aliilapro.ir/Proxy/)
- [Official README](https://github.com/ALIILAPRO/Proxy#readme)
- [Project repository](https://github.com/ALIILAPRO/Proxy)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/aliilapro-proxy