Is 77.245.102.106:3128 a proxy? Yes, it was.
77.245.102.106:3128 was a public proxy in the HProxy free proxy pool, exiting from KZ on KTC-AS. Across 458 checks it answered 11% of the time, and it has since gone dark (last listed 2026-07-14), so it is not a usable proxy right now.
uptime while tracked
KazakhstanUptime & downtime
0
Days tracked
0
Checks run
—
Downtime
0
Down days
Continuous monitoring
How HProxy checks 77.245.102.106:3128
HProxy has checked 77.245.102.106:3128 458 times and it answered 49 of those. Here is what each of those checks actually did.
36 public sources published it
77.245.102.106 appears in 36 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 3128: Squid default
Port 3128 is the default listening port for Squid, the most widely deployed caching proxy in the world. Most addresses published on 3128 are Squid installations that were left reachable from the public internet rather than restricted to a local network.
Every check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens an actual connection to 77.245.102.106:3128 and waits up to 4 seconds for the other end to complete a proxy handshake. 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.
458 checks, 49 answered
That is 11% of the time, measured since July 8, 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. 77.245.102.106:3128 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 24 hours. Its last check was on August 3, 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.
This endpoint
The record
Everything HProxy holds on 77.245.102.106:3128, and nothing it does not.
- First seen
- July 8, 2026
- Last checked
- August 3, 2026
- Next check due
- within 24 hours
- Checks run
- 458
- Times it answered
- 49
- Stopped answering
- July 14, 2026
11%
answered 49 of 458 checks
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds no other free proxies on AS35104 right now, and 16 in Kazakhstan. 77.245.102.106:3128 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
What HProxy holds on KTC-AS
Open proxies are not spread evenly across the internet. They cluster, because one misconfigured template, one cheap hosting reseller or one leaked image tends to produce hundreds of identical machines on the same network. HProxy tracks 10 addresses on AS35104, which is 0.00% of every address in the database and a small corner of the database. None of them are answering at the moment, though every one stays in the re-check rotation in case that changes.
- Answered before10%
- Never answered90%
Questions about 77.245.102.106:3128
Is 77.245.102.106:3128 a working proxy?
No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last listed 2026-07-14. We still re-test it periodically in case it returns.
Was 77.245.102.106 ever actually a proxy?
Yes. We ran 458 checks against it and it answered 49 of them, about 11% of the time, over 6 days on our list.
Where was 77.245.102.106 hosted?
Kazakhstan — KTC-AS (AS35104). It is a residential or ISP address rather than a datacenter one.
Why keep a page for an address that no longer works?
Because "was this address ever a proxy, and when" is a real question. If you are looking at this IP in a firewall log or an abuse report, the dates and the check counts here are the answer. HProxy's public proxy IP list keeps every address it has ever tracked and carries on re-testing them, so deleting this record would throw all of that away.
How many free proxies are on AS35104?
None other than 77.245.102.106:3128 at the moment. AS35104 (AS35104) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Kazakhstan?
Yes, 16 free proxies are exiting from Kazakhstan in our pool right now, answering in 4731ms at the median. If this address is not usable, that list is the place to look for a working one.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.