Is 167.233.124.193:9112 a proxy? It was listed.

31 public sources published it

167.233.124.193 appears in 31 of the public proxy sources HProxy tracks. Lists copy from each other constantly, so an address showing up in many of them says a lot about how widely it was republished and very little about whether it ever worked.

Port 9112: Registered port range

This port sits in the middle range, where any ordinary program can listen without special permission. The number itself carries no reserved meaning, which tells you somebody picked it on purpose instead of accepting a default.

Every failure here was measured, not assumed

Each check opens a real connection to 167.233.124.193:9112 and gives it up to 90 seconds to answer. Slow is not the same as dead, and plenty of working proxies take half a minute to reply. Nothing about this record is inherited from the list that published the address. 13 times HProxy tried, and 13 times the connection did not complete inside that budget, which is why the answer on this page is a flat no rather than a maybe. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, so a proxy is never missed because we guessed the wrong protocol.

13 checks, zero connections

Not one of those 13 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 13 times and it never answered" is a far more useful answer than silence for anyone who found 167.233.124.193 somewhere and wants to know what it is.

It is still re-tested every 24 hours

167.233.124.193:9112 has never answered, and it is still in the rotation anyway. The sweep reaches every address in the database roughly once every 24 hours regardless of its history, because an address that was dark for months can be brought back online by whoever controls it without telling anybody. Its last check was on August 8, 2026, so the next one is due within a day of that. If that ever happens here, this page changes on its own.