Is 174.138.163.53 a proxy? Yes, it was.
174.138.163.53 has been a working public proxy: 49 of the 91 ports we track on it have answered our checks at some point. None are answering right now, and we are still testing all of them.
ports recorded on this address
United StatesPorts recorded on 174.138.163.53
We hold 91 ports on 174.138.163.53 and have run 8,150 checks against them. 49 ports have answered at some point, though none are answering right now. Open any port for its full record.
| Port | Status | Times answered |
|---|---|---|
| 35607 | Not responding | 3 / 226 |
| 8001 | Not responding | 2 / 230 |
| 9408 | Not responding | 2 / 238 |
| 33371 | Not responding | 2 / 226 |
| 34963 | Not responding | 2 / 235 |
| 36370 | Not responding | 2 / 228 |
| 51122 | Not responding | 2 / 232 |
| 54433 | Not responding | 2 / 236 |
| 8080 | Not responding | 1 / 32 |
| 8092 | Not responding | 1 / 32 |
| 8192 | Not responding | 1 / 32 |
| 8254 | Not responding | 1 / 32 |
| 9461 | Not responding | 1 / 32 |
| 9786 | Not responding | 1 / 32 |
Show the other 77 ports on this page
| Port | Status | Times answered |
|---|---|---|
| 21311 | Not responding | 1 / 32 |
| 21799 | Not responding | 1 / 32 |
| 23677 | Not responding | 1 / 32 |
| 30196 | Not responding | 1 / 32 |
| 30566 | Not responding | 1 / 32 |
| 30592 | Not responding | 1 / 235 |
| 30792 | Not responding | 1 / 32 |
| 31544 | Not responding | 1 / 32 |
| 32334 | Not responding | 1 / 228 |
| 33366 | Not responding | 1 / 32 |
| 33529 | Not responding | 1 / 32 |
| 33949 | Not responding | 1 / 32 |
| 34005 | Not responding | 1 / 32 |
| 35605 | Not responding | 1 / 32 |
| 36440 | Not responding | 1 / 32 |
| 37255 | Not responding | 1 / 222 |
| 37416 | Not responding | 1 / 232 |
| 38687 | Not responding | 1 / 223 |
| 38727 | Not responding | 1 / 236 |
| 38831 | Not responding | 1 / 32 |
| 39979 | Not responding | 1 / 32 |
| 50288 | Not responding | 1 / 32 |
| 50830 | Not responding | 1 / 231 |
| 50834 | Not responding | 1 / 32 |
| 51275 | Not responding | 1 / 32 |
| 54216 | Not responding | 1 / 231 |
| 54315 | Not responding | 1 / 32 |
| 55153 | Not responding | 1 / 222 |
| 55155 | Not responding | 1 / 32 |
| 55335 | Not responding | 1 / 32 |
| 56418 | Not responding | 1 / 232 |
| 56651 | Not responding | 1 / 32 |
| 56718 | Not responding | 1 / 32 |
| 57398 | Not responding | 1 / 32 |
| 65248 | Not responding | 1 / 228 |
| 8056 | Not responding | 0 / 30 |
| 8509 | Not responding | 0 / 30 |
| 8806 | Not responding | 0 / 29 |
| 9984 | Not responding | 0 / 30 |
| 20224 | Not responding | 0 / 29 |
| 20630 | Not responding | 0 / 30 |
| 21612 | Not responding | 0 / 29 |
| 30672 | Not responding | 0 / 30 |
| 30866 | Not responding | 0 / 29 |
| 31406 | Not responding | 0 / 30 |
| 31472 | Not responding | 0 / 30 |
| 31705 | Not responding | 0 / 30 |
| 31838 | Not responding | 0 / 29 |
| 32650 | Not responding | 0 / 29 |
| 34699 | Not responding | 0 / 30 |
| 34955 | Not responding | 0 / 30 |
| 34965 | Not responding | 0 / 220 |
| 35556 | Not responding | 0 / 29 |
| 36232 | Not responding | 0 / 29 |
| 36359 | Not responding | 0 / 29 |
| 38660 | Not responding | 0 / 30 |
| 50086 | Not responding | 0 / 29 |
| 50441 | Not responding | 0 / 30 |
| 50495 | Not responding | 0 / 30 |
| 51221 | Not responding | 0 / 30 |
| 51294 | Not responding | 0 / 30 |
| 51804 | Not responding | 0 / 30 |
| 52202 | Not responding | 0 / 232 |
| 52214 | Not responding | 0 / 222 |
| 54806 | Not responding | 0 / 29 |
| 54860 | Not responding | 0 / 234 |
| 55459 | Not responding | 0 / 219 |
| 55646 | Not responding | 0 / 224 |
| 55666 | Not responding | 0 / 30 |
| 55743 | Not responding | 0 / 230 |
| 55954 | Not responding | 0 / 29 |
| 56661 | Not responding | 0 / 29 |
| 56950 | Not responding | 0 / 232 |
| 57266 | Not responding | 0 / 30 |
| 57368 | Not responding | 0 / 30 |
| 57597 | Not responding | 0 / 30 |
| 65087 | Not responding | 0 / 29 |
Questions about 174.138.163.53
Is 174.138.163.53 a proxy?
Not at this moment, but it has been. 49 of the 91 ports we track on 174.138.163.53 have answered at some point while we were watching. We keep re-testing all of them, so any could come back.
Why does 174.138.163.53 have so many ports listed?
Public proxy lists are often built by scanning a machine and publishing every port that looks open, so one address can end up republished dozens or thousands of times over. HProxy records each ip:port separately because they genuinely are separate endpoints, tests each one, and keeps the result. That is why this page can tell you how many of them were ever real.
How long have you been tracking 174.138.163.53?
Since May 13, 2026. We have run 8,150 checks against this address since then and we have not stopped: every endpoint on it is re-tested on a schedule, whether or not it has ever answered.
Free proxies answering right now
View all →
185.26.180.180:80
HTTP · Netherlands · 100% · 24ms
104.155.15.30:80
HTTP · Belgium · 100% · 27ms
13.38.217.179:5283
HTTP · France · 17% · 28ms
13.38.217.179:42820
HTTP · France · 18% · 30ms
15.237.108.20:1743
HTTP · France · 14% · 33ms
3.127.27.51:34884
HTTP · Germany · 13% · 35ms
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.
Starting from
$0.44/GB
Billed per GB · balance never expires
Get started free→Compare plans & pricingAbout 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.