Is 176.222.53.103:88 a proxy? Yes.
176.222.53.103:88 is a public HTTP proxy in the HProxy free proxy list, exiting from Netherlands. It holds an excellent 100% uptime with a high 15810ms response time, and was last checked 21 min ago.
uptime
How this one compares
Reliable enough to sit in the top 5% of everything we are watching.
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,940 proxies answering right now, the middle of the pack answers 26.6% of the checks we send it.
100%
of 92 checks answered
Pool median 26.6%. 176.222.53.103:88 is in the top 5%.
15810ms
on its last response
Pool median 5,854ms.
1
days tracked, still in the live pool
Of the 271,565 free proxies we have watched stop working, half were gone within 26 days of us first seeing them.
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 271,565 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 4,940 proxies answering right now.
Where this address sits
Right now our free pool holds 3 other free proxies on Hostkey AS, and 215 in Netherlands. 176.222.53.103:88 sits inside that set, so if it is not usable the pages below are where its closest alternatives are. At 15810ms it is slower than the 772ms median for Netherlands proxies.
HOSTKEY-AS is the 137th largest source of free proxies we have ever measured.
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 326 addresses on AS57043, which is 0.04% of every address in the database and a small corner of the database. That makes it the 137th largest source of free proxies of every network we have ever seen. 4 of them are answering right now, so if this particular address is not usable, the network is a reasonable place to look for one that is.
- Answering now1%
- Answered before45%
- Never answered54%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS1943779,187
- 3SECURED SERVERS LLCAS2045447,188
- 4Amazon.com, Inc.AS1650944,498
- 5Cloudflare, Inc.AS1333522,923
- 6M247AS900918,966
- 7Cloudflare, Inc.AS20924214,275
- 8Alibaba (US) Technology Co., Ltd.AS4510212,247
128 networks between
137HOSTKEY-ASAS57043326
How to use this proxy
Route a request through 176.222.53.103:88 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://176.222.53.103:88 \
https://api.ipify.org?format=json
Not a terminal person? Pick your device and we walk you through it, nothing assumed.
Continuous monitoring
How HProxy checks 176.222.53.103:88
176.222.53.103:88 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 88: 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.
It has answered every single check
Each check opens a real connection to 176.222.53.103:88 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. 176.222.53.103:88 has completed that handshake on all 92 attempts so far, which is rare on a free public proxy and worth treating with some suspicion until the record is longer. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, which is how we know it spoke HTTP.
92 checks, 92 answered
That is 100% of the time, measured since September 11, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
It is being re-tested continuously
176.222.53.103:88 is in the live rotation, so it is re-tested continuously rather than on a daily cycle. If it stops answering it is marked down immediately, and if it stays down for 3 days it moves into the public proxy database with its full record intact. Nothing is deleted at any point.
This endpoint
The record
Everything HProxy holds on 176.222.53.103:88, and nothing it does not.
- First seen
- September 11, 2026
- Last checked
- September 12, 2026
- Next check due
- continuously
- Checks run
- 92
- Times it answered
- 92
- Spoke
- HTTP
100%
answered 92 of 92 checks
Questions about 176.222.53.103:88
Is 176.222.53.103:88 a working proxy right now?
Yes. 176.222.53.103:88 answered HProxy's automated check 21 min ago and is in the live free proxy pool as we publish this page. It is re-tested every few minutes, so open this page again for its current state rather than trusting a copy of it.
What kind of proxy is 176.222.53.103?
It speaks HTTP, and our checks grade it transparent. The port is 88. Point your client at 176.222.53.103:88 over http to route a request through it.
Where is 176.222.53.103 located?
Traffic through it exits from Amsterdam, Netherlands, on HOSTKEY-AS (AS57043). That is where the destination site will think your request came from.
How fast is 176.222.53.103:88?
It answered in 15810ms on the last check. Free public proxies are shared, so real-world speed varies with how many other people are using it at the same moment.
How reliable has 176.222.53.103:88 been?
Across 2 days of tracking it answered 100% of our checks. The chart on this page shows every day we have recorded for it, including the days it was down.
Is it safe to use 176.222.53.103:88?
Treat it the way you would any public proxy: it is operated by someone we have no relationship with, it is shared with strangers, and anything you send unencrypted over it can be read. Fine for a quick geo check or a scrape of public data, never for logins, payments or anything private.
How many free proxies are on Hostkey AS?
3 other free proxies are live on Hostkey AS (AS57043) in our pool right now, alongside 176.222.53.103:88. Networks that host one open proxy usually host several, which is why the whole AS is worth browsing rather than just this address.
Are there other free proxies in Netherlands?
Yes, 215 free proxies are exiting from Netherlands in our pool right now, answering in 772ms 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
This one is good, and it will still disappear.
176.222.53.103:88 has answered 100% of our checks, which puts it well above most of what we track. It is still a public endpoint with nobody standing behind it: nobody agreed to serve you, no capacity is set aside for you, and there is no warning on the day it stops. Fine for a test, a bad foundation for anything that has to work tomorrow.
Other live free proxies
View all31.207.44.151:1080
SOCKS5 · Netherlands · 40% · 75ms
66.151.34.89:80
HTTP · Finland · 98% · 157ms
82.26.94.232:3128
HTTP · Türkiye · 61% · 5975ms
151.243.176.163:8081
HTTP · United Arab Emirates · 56% · 19491ms
195.26.224.135:80
HTTP · Netherlands · 82% · 50ms
95.211.174.135:3128
HTTP · Netherlands · 57% · 65ms
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.