# hideip.me: five text files, no generator, no licence, and a badge for an IPv6 list that does not exist

> hideip.me publishes open proxies it collects from the internet, refreshed on a ten minute cycle, and its own note says it is not responsible for them. There is no code here to audit: six entries, five of them plain text lists, and the process that fills them runs somewhere outside the repository. The two usage examples the page does give both turn off certificate verification, which tells you more about the posture than any feature list would.

**zloi-user/hideip.me** —   proxy list that updates every 10 minutes

- Repository: https://github.com/zloi-user/hideip.me
- Website: https://hideip.me/en/proxy
- Stars: 510 · Forks: 32
- Language: Unknown
- License: not declared
- Published: 2026-08-21 · Updated: 2026-08-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/zloi-user-hideip-me

## Five text files and a cron job that is not in the repository

The entire repository is six entries: `README.md`, `connect.txt`, `http.txt`, `https.txt`, `socks4.txt`, and `socks5.txt`. There is no source directory, no `package.json`, no requirements file, no `Dockerfile`, no `.github/`, and no CI configuration. The primary language is recorded as unknown and the licence as unknown, with no licence file among those six entries either. So the claim in the repository description, that the list updates every ten minutes, describes a process that lives somewhere other than here. The only evidence that the promise is being kept is the commit timestamp, and the last push recorded is 2026-10-01 at 17:44 UTC. A reader who wants to know how these addresses are obtained, how duplicates are removed, or whether a dead entry is ever dropped has nothing to read and nothing to run.

## The opening badge points at an IPv6 list the repository does not contain

The first thing on the page is a link to `hideip.me/en/proxy6`, which is the site's IPv6 proxy listing. The repository ships five files and none of them is an IPv6 list. There is no `socks6.txt`, no `http6.txt`, and no separate directory for IPv6 addresses, so the entry point on the site and the data in the repository describe different sets. The five that do exist are served raw from the `main` branch, which is why the links use the `raw/refs/heads/main/` path form rather than pointing at release assets:

```bash
https://github.com/zloi-user/hideip.me/raw/refs/heads/main/connect.txt
```

Serving data from a branch rather than from a tagged release means the URL has no version. Two clients fetching that address an hour apart can get different lists, and there is no way to pin or reproduce what you saw.

## Every usage example instructs you to stop verifying certificates

The page gives two ways of routing a request through one of these proxies, one using curl on Linux and one launching Chrome on Windows with a throwaway profile directory. Both carry flags whose only purpose is to make an untrusted certificate acceptable: the curl examples pass a flag that skips verification on the proxy connection and a second that skips it on the target, and the Chrome example passes the two flags that disable certificate errors and SSL errors. That is the correct posture for a MITM inspection proxy and the wrong posture for an open proxy you found on the internet, where the entire point of TLS is that the hop in the middle cannot read you. The verification target in both examples is a plain HTTP endpoint that echoes the caller's address, so even the connectivity check itself goes out unencrypted to a third party.

## CONNECT is a forwarding method, not a protocol, and its list overlaps the HTTP one

The five lists are presented as five categories: HTTP, HTTPS, SOCKS4, SOCKS5, and CONNECT. The last is not a protocol. CONNECT is an HTTP method by which a client asks an HTTP proxy to open a tunnel, and it is the mechanism the second curl example exercises with a tunnel flag. So `connect.txt` is not a family of endpoints distinct from `http.txt`; it is a subset of plain HTTP proxies distinguished by whether they permit tunnelling. `https.txt` is the other half of that split, being proxies that accept TLS on the proxy connection itself. A reader choosing one list by name has to know which of the two HTTP lists they actually want, and the page does not say which is the safer expectation, only that the HTTPS example needs certificate flags to get past a certificate nobody controls.

## A disclaimer, four donation channels, and no terms

The one substantive statement of policy is a note that the list is collected from proxies available on the internet, is displayed in the repository for easy access, and that the maintainer is not responsible for proxies. That is a reasonable disclaimer for content nobody owns, and it is the only one. There is no terms file, no acceptable use policy, no reporting address, and no licence, so nothing states what a reader may do with the data or what happens to a request that arrives through one of these addresses and lands on the maintainer. Below the disclaimer sit four donation channels: a USDT address on TRC-20, a Bitcoin mainnet address, a WebMoney link covering Ethereum and Litecoin among others, and a YooMoney card link. A repository with no code and one licence-free text file per proxy family carries the same donation surface as a project with a build.

## The repository is named after a site that also sells private proxies

The repository is called `hideip.me` and its homepage is `https://hideip.me/en/proxy`, so the code host mirrors the product name rather than the other way round. The page closes with one more link, `hideip.me/en/privateproxies`, which is the site's paid tier. The structure is therefore a free list of addresses collected from strangers, published without liability, pointing at a commercial page selling managed proxies. The naming also invites a specific confusion: the repository description begins with two leading spaces and then reads proxy list that updates every 10 minutes, a fragment missing its article, and the surrounding brand is one a reader could easily file under consumer anonymity software. Nothing in the six repository entries separates this data feed from that category.

## Conclusion

Treat hideip.me as a data feed, not as software. There is nothing to install, nothing to build, and nothing to review before you depend on it: the generator is absent, the licence is unknown, the language is unrecorded, and the only audit trail is a commit timestamp that moves every ten minutes. Before you point anything at these addresses, understand that you are routing through hardware you do not control and that the page's own examples instruct you to stop verifying certificates, which removes the only protection that would tell you the hop has been tampered with. If your use is authorised testing of your own systems, keep it to that, and treat any list you pull as hostile input to be validated rather than trusted.

## FAQ

### What is in the hideip.me repository?

Six entries: `README.md` and five plain text files named `http.txt`, `https.txt`, `socks4.txt`, `socks5.txt`, and `connect.txt`. There is no source code, no build configuration, and no licence file.

### How often does hideip.me update its proxy lists?

The repository description states the list updates every ten minutes. No generator, scheduler, or CI workflow is included in the repository, so the mechanism that refreshes the files is not visible here.

### Does hideip.me state any terms for using the proxies?

The only statement is a note that the list is collected from proxies available on the internet, is displayed for easy access, and that the maintainer is not responsible for proxies. There is no licence file, terms page, or acceptable use policy in the repository.

### Which proxy protocols does hideip.me publish lists for?

Five files covering HTTP, HTTPS, SOCKS4, SOCKS5, and CONNECT. CONNECT is a tunnelling method used by HTTP proxies rather than a separate protocol, so the two HTTP lists split plain proxies by whether they accept TLS on the proxy connection or by whether they permit tunnelling.

## Sources

- [Official documentation](https://hideip.me/en/proxy)
- [Official README](https://github.com/zloi-user/hideip.me#readme)
- [Project repository](https://github.com/zloi-user/hideip.me)

---

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