mubeng is a free, open-source proxy checker and IP rotator written in Go, published on GitHub by Dwi Siswanto under the Apache 2.0 license. Its last release, v0.23.0, came out on August 2, 2025. On October 23, 2026, the one outside service that every check rests on still answered, and so did its update check.
This page sets out what mubeng does, how it decides that a proxy works, and what has changed since its last release. It ends with the free command-line checker we maintain. We did not download or run mubeng: everything about its behavior comes from its own code and records on GitHub.
What does mubeng do?
It does two jobs. With --check, it tests a list of proxies and prints the live ones. With -a and an address, it runs a local proxy server that sends requests through the proxies on your list. By default it moves to the next proxy after every request, in order, and it can also pick at random.
It reads HTTP, HTTPS, SOCKS4, SOCKS4A and SOCKS5 lines, and its rotator also takes Amazon API Gateway. Each line needs its scheme, such as http:// or socks5://. A line without one is skipped, and so is a duplicate. Its releases carry files for Windows, Linux and macOS, ARM included, and there is a Docker image.
How does mubeng decide that a proxy works?
Every check sends one request through the proxy to one outside address, ipinfo.io/json. If that service's JSON comes back within the wait, the proxy counts as live. mubeng then prints the exit address, its country and the time taken. Since v0.23.0, --output-format can also print the city, region, network and timezone from the same answer.
The defaults are 30 seconds per check, 50 checks at a time and no retries. Three things follow from its code:
- No anonymity grade. mubeng reads only what ipinfo.io reports about the exit. It never sees the headers that reached the far end, so it cannot tell a transparent proxy that forwards your address from an elite one. Our guide to anonymity levels explains the difference.
- One protocol per line. It uses the scheme written in the line, so a SOCKS5 proxy listed as
http://fails. - No certificate checks. Its client accepts any certificate, with TLS 1.0 as the floor and, since April 2025, older cipher suites allowed. A proxy that re-signs HTTPS in order to read it passes like any other.
How popular is mubeng?
On October 23, 2026, the repository counted 2,772 stars and 278 forks. Its release files had been downloaded 44,236 times across 40 releases. Version 0.23.0 alone counted 16,894, and 13,891 of those were the Linux file for 64-bit machines. A download counter counts files fetched, and it cannot tell how many copies run.
Interest is rising. Google searches for mubeng went from 590 a month in October 2025 to 1,300 in September 2026. Releases went the other way:
Is mubeng still maintained?
Its last code change, the custom output format, came with v0.23.0 on August 2, 2025. The repository has had two commits since, both to the documentation: sponsors were added on August 17, 2026, and taken out again on September 9. The project is not archived.
On October 23, 2026, 18 issues and 13 pull requests were open. On August 9, 2026, four reports arrived, each with a pull request that fixes it. One pair was closed, and the other three are still open. A pull request its author opened in June 2025 would move the check to another address service. It is still open.
What do its checks depend on?
On one outside service. Until March 2023 mubeng asked a different address service, which a user reported going down at times. On March 9, 2023, it moved to ipinfo.io, which it still uses. Its update command reads its version list from GitHub. We asked each of these addresses once, from a server, on October 23, 2026, and sent nothing through any proxy:
Everything answered. The answer from ipinfo.io carries a readme field that points to IPinfo's page for requests made without a token. That page calls them its "Legacy Free API", says such requests are "limited to 50k requests/month" and that they receive "limited data". So every mubeng check rests on one company's free service, used without a key. If that service changes, working proxies would show up as dead until mubeng changes too.
The update check asks for the changelog under the repository's earlier owner name. GitHub redirects a moved repository's old address, so it still reached the release.
What do its users ask for?
The issue tracker shows the gaps. A 2025 user asked whether it runs on Windows, and it does. A 2023 report that it cannot run as a Windows service is still open, and so is a 2024 request for an HTTPS proxy server. Two 2022 reports describe trouble installing its certificate for the rotator.
Older requests were met. A 2022 report of wrong results at very high concurrency led to the setting for checks at a time. The 2023 outage report led to the move to ipinfo.io.
A free checker that is maintained: the HProxy command-line tool
We make a free proxy checker, and we sell residential proxies, so read this part with that in mind. Our app comes with a command-line tool, hproxy, built on the same engine. The app and the tool are free, MIT-licensed and public on GitHub, for Windows, macOS and Linux.
| mubeng v0.23.0 | hproxy | |
|---|---|---|
| Checks against | ipinfo.io/json | our own judges, with a one-time code |
| Reports | live, exit, country, time | protocols, anonymity, exit, time |
| Protocols per line | the scheme in the line | all four, tried at once |
| Line formats | with a scheme | any shape a provider prints |
| Default wait | 30 seconds | 8 seconds per attempt |
| At once | 50 | up to 64 |
| Re-signed HTTPS | not checked | flagged |
| AI assistants | none | an MCP server |
| License | Apache 2.0 | MIT |
- It reads any shape a provider prints. That covers
host:port,host:port:user:pass,user:pass@host:port,socks5://lines and CSV, from arguments, a file or a pipe. - It tries HTTP, HTTPS, SOCKS4 and SOCKS5 on every line at once, from your own machine, and prints each row the moment it settles. A proxy locked to your IP can only be tested from that IP.
- Its judges run on our own domain. Our reflector returns the address it saw and every header, for a full anonymity grade, and Cloudflare's trace page on our domain is the fallback. A proxy counts only when the judge returns a one-time code.
- It flags a proxy that re-signs HTTPS, in a field of its own.
- It fits scripts.
--json,--fields,--aliveand--firstshape the output, and its exit codes follow grep: 0 when something works, 1 when nothing does, 2 when it could not run. - Location is opt-in.
--geoadds each exit's country and network, and it sends only the exit addresses to our IP lookup. - It connects too.
hproxy connectruns a local proxy without a password, HTTP and SOCKS5 on one port, and rotates a list every request, every N requests, at random or on failure. - It serves AI assistants.
hproxy mcpoffers the same checks and connections over MCP.
hproxy check --file proxies.txt --alive --geo
hproxy check --file proxies.txt --json > checked.jsonl
Get the app, with the tool inside, on our proxy checker page.
Or check a list online
If you would rather install nothing, our online proxy checker runs in the browser. It takes up to 100,000 lines a run, and 300,000 a day from one address, with no account. It tries HTTP, HTTPS, SOCKS4 and SOCKS5 on every line. It cannot reach a proxy locked to your own IP address, which the app and the tool can.
To read the results, our guides on checking if a proxy works and on proxy speed and latency explain each column. Our page on UnFX Proxy Checker looks at another free checker the same way.
Where HProxy fits
The checkers are free. What we sell is residential proxies: Residential Lite costs $0.50/GB for one GB, falling to $0.44/GB at 2,000 GB+, and the balance does not expire. If a free list keeps failing your checks, a paid pool is the next step, and you can test it with the same tools.
What we could not find out
We did not run mubeng, so we cannot say how its current build behaves on a given machine. IPinfo's page does not say whether its monthly limit counts per key, per address or otherwise for requests that arrive through many proxies. Our check is one request to each address from one server at one moment. GitHub's counters count files fetched, never users, and the Linux file's count may include automated downloads.
Sources
- mubeng's repository on GitHub (mubeng/mubeng, moved from kitabisa/mubeng): its record, README, internal/checker, internal/runner/options.go, pkg/mubeng/transport.go, internal/proxymanager and internal/updater, read as text on October 23, 2026.
- GitHub's records of its 40 releases with their download counters, its commits, the history of internal/checker/vars.go, and issues #143, #149, #159, #191, #215, #220, #251, #283 and #300, read October 23, 2026.
- IPinfo's page on requests without a token, read through our server on October 23, 2026.
- GitHub Docs on transferring a repository, read October 23, 2026.
- Our own check from a server on October 23, 2026: ipinfo.io/json and mubeng's two update addresses.
- Google Keyword Planner, worldwide monthly searches for mubeng, October 2025 to September 2026.
- HProxy's command-line tool and engine code: the usage text, the MCP server, the result rows, the judges and the HTTPS interception field.
