Is 82.102.11.164:3460 a proxy? Yes, it was.

53 public sources published it

82.102.11.164 appears in 53 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 3460: 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 check is a real connection

HProxy does not read this address off somebody else's list and pass it on. Each check opens a real connection to 82.102.11.164:3460 and gives it up to 90 seconds to answer. Slow is not the same as unreachable, and plenty of working proxies take half a minute to reply. Anything that does not answer in that budget counts as a failure and is recorded as one, which is why the percentage on this page moves rather than sitting at a marketing number. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, so a proxy is never missed because we guessed the wrong protocol.

1,915 checks, 906 answered

That is 47% of the time, measured since June 11, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.

We are still watching for it to come back

Being archived does not stop the testing. 82.102.11.164:3460 answered before, so it is exactly the kind of address that can return, and the sweep works through the whole database and reaches every address roughly once every 12 hours. Its last check was on September 6, 2026, so the next one is due within a day of that. The moment it answers again it is promoted straight back into the live free proxy list, automatically, with no manual step.