Is 128.241.233.174:808 a proxy? Yes, it was.
128.241.233.174:808 was a public proxy in the HProxy free proxy pool, exiting from United States on TF. Across 190 checks it answered 1% of the time, and it has since gone dark (last answered July 31, 2026), so it is not a usable proxy right now.
across all 190 checks
United StatesUptime & downtime
3
Days tracked
155
Checks run
100%
Downtime
3
Down days
How this one compares
It worked sometimes, for 5 days, and then it stopped.
Every free proxy list quotes an uptime figure. Almost none of them tell you what a normal one looks like, so here is ours: across the 4,413 proxies answering right now, the middle of the pack answers 15.5% of the checks we send it.
1%
of 190 checks answered
Pool median 15.5%. 128.241.233.174:808 sits below it, which is ordinary for a public proxy.
190
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
5
days from first sighting to last answer
Of the 195,249 free proxies we have watched stop working, half were gone within 28 days of us first seeing them.
July 26, 2026
First listed by our sources
Published as a working proxy by 2 of the public lists HProxy tracks. Being listed is a claim, not a test.
July 31, 2026
Stopped answering
It answered our checks for 5 days before it went quiet.
August 3, 2026
Moved to the permanent record
It left the live pool here. Nothing is deleted: the address keeps this page and stays in the re-check rotation.
August 17, 2026
Most recent re-test
HProxy has opened 190 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 24 hours.
What normal looks like
Every number above is measured against these two.
A percentage on a proxy list means nothing without the shape of the thing it came from. These are the two distributions the rest of this page compares against, drawn from HProxy's own checks rather than from anybody's marketing page.
How long one lasts
Days from the first time we saw an address to the last time it answered, across 195,249 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 4,413 proxies answering right now.
Continuous monitoring
How HProxy checks 128.241.233.174:808
HProxy has checked 128.241.233.174:808 190 times and it answered 1 of those. Every one of those was a real connection attempt, never a lookup.
2 public sources published it
128.241.233.174 appears in 2 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 808: System port
Ports below 1024 are protected. On most systems you need administrator rights to open one at all. So whatever is answering here was set up by someone with full control of that machine, not by some ordinary program that happened to be running.
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 128.241.233.174:808 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.
190 checks, 1 answered
That is 1% of the time, measured since July 26, 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. 128.241.233.174:808 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 17, 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 128.241.233.174:808, and nothing it does not.
- First seen
- July 26, 2026
- Last checked
- August 17, 2026
- Next check due
- within 24 hours
- Checks run
- 190
- Times it answered
- 1
- Stopped answering
- July 31, 2026
1%
answered 1 of 190 checks
Live free proxies right now
View all →34.207.102.197:18643
HTTPS · United States · 27% · 317ms
18.188.53.175:137
SOCKS4 · United States · 9% · 322ms
18.188.168.99:1080
HTTP · United States · 13% · 340ms
3.19.213.118:26514
HTTPS · United States · 16% · 341ms
18.222.132.180:30664
HTTPS · United States · 12% · 348ms
18.190.253.157:6406
SOCKS4 · United States · 11% · 350ms
Where this address sits
Right now our free pool holds no other free proxies on TF, and 888 in United States. 128.241.233.174:808 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
How many free proxies are on TF
Open proxies cluster rather than spreading evenly across the internet. Hosting providers and cloud platforms run enormous numbers of near-identical servers, so a handful of networks end up carrying a disproportionate share of every public proxy list, including ours. HProxy tracks 7 addresses on AS213802, 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 before57%
- Never answered43%
- 1LimitedNetwork-ASAS213790227,266
- 2Amazon.com, Inc.AS1650928,656
- 3Cloudflare, Inc.AS1333522,186
- 4SECURED SERVERS LLCAS2045419,475
- 5Cloudflare, Inc.AS20924214,141
- 6Alibaba (US) Technology Co., Ltd.AS4510211,708
- 7GloboTech CommunicationsAS3666611,542
- 8ChinanetAS41348,411
- AS213802 sits outside the 250 largest networks we hold.
Questions about 128.241.233.174:808
Is 128.241.233.174:808 a working proxy?
No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last answering on July 31, 2026. We still re-test it periodically in case it returns.
Was 128.241.233.174 ever actually a proxy?
Yes. We ran 190 checks against it and it answered 1 of them, about 1% of the time, over 5 days on our list.
What is the hostname for 128.241.233.174?
128.241.233.174 publishes no reverse DNS record. That is not unusual and it is not suspicious on its own, but it does mean the address volunteers nothing about who runs it, so the network and the check history below are all there is to go on.
Where was 128.241.233.174 hosted?
San Jose, California, United States, TF (AS213802). 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 TF?
None other than 128.241.233.174:808 at the moment. AS213802 (TF) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in United States?
Yes, 888 free proxies are exiting from United States in our pool right now, answering in 1685ms at the median. If this address is not usable, that list is the place to look for a working one.
Where to go next
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.