Is 174.138.162.238 a proxy? Yes, it was.
174.138.162.238 has been a working public proxy: 79 of the 89 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.162.238
We hold 89 ports on 174.138.162.238 and have run 23,958 checks against them. 79 ports have answered at some point, though none are answering right now. Open any port for its full record.
| Port | Status | Times answered |
|---|---|---|
| 8001 | Not responding | 37 / 251 |
| 8254 | Not responding | 23 / 263 |
| 8220 | Not responding | 22 / 256 |
| 20121 | Not responding | 16 / 480 |
| 31816 | Not responding | 15 / 452 |
| 9405 | Not responding | 13 / 468 |
| 39458 | Not responding | 12 / 454 |
| 56247 | Not responding | 12 / 456 |
| 30404 | Not responding | 11 / 238 |
| 37874 | Not responding | 11 / 472 |
| 38912 | Not responding | 11 / 464 |
| 39917 | Not responding | 11 / 465 |
| 52784 | Not responding | 11 / 258 |
| 8019 | Not responding | 10 / 233 |
Show the other 75 ports on this page
| Port | Status | Times answered |
|---|---|---|
| 8109 | Not responding | 10 / 211 |
| 33393 | Not responding | 10 / 249 |
| 36646 | Not responding | 10 / 467 |
| 35964 | Not responding | 9 / 462 |
| 53117 | Not responding | 9 / 256 |
| 58196 | Not responding | 9 / 442 |
| 54134 | Not responding | 8 / 249 |
| 55302 | Not responding | 8 / 447 |
| 62837 | Not responding | 8 / 463 |
| 8778 | Not responding | 7 / 240 |
| 31649 | Not responding | 7 / 243 |
| 36831 | Not responding | 7 / 253 |
| 39238 | Not responding | 7 / 245 |
| 8092 | Not responding | 6 / 242 |
| 8228 | Not responding | 6 / 249 |
| 9404 | Not responding | 6 / 449 |
| 21523 | Not responding | 6 / 244 |
| 22291 | Not responding | 6 / 448 |
| 50886 | Not responding | 6 / 241 |
| 51891 | Not responding | 6 / 237 |
| 53450 | Not responding | 6 / 464 |
| 56431 | Not responding | 6 / 251 |
| 22129 | Not responding | 5 / 206 |
| 30559 | Not responding | 5 / 244 |
| 34461 | Not responding | 5 / 253 |
| 36122 | Not responding | 5 / 254 |
| 36958 | Not responding | 5 / 432 |
| 38204 | Not responding | 5 / 412 |
| 52330 | Not responding | 5 / 239 |
| 54110 | Not responding | 5 / 251 |
| 54750 | Not responding | 5 / 239 |
| 55344 | Not responding | 5 / 447 |
| 55636 | Not responding | 5 / 241 |
| 55694 | Not responding | 5 / 447 |
| 32055 | Not responding | 4 / 242 |
| 34932 | Not responding | 4 / 239 |
| 36239 | Not responding | 4 / 440 |
| 38298 | Not responding | 4 / 236 |
| 39142 | Not responding | 4 / 240 |
| 35798 | Not responding | 3 / 242 |
| 37439 | Not responding | 3 / 31 |
| 38215 | Not responding | 3 / 237 |
| 39083 | Not responding | 3 / 238 |
| 39768 | Not responding | 3 / 244 |
| 50890 | Not responding | 3 / 237 |
| 51771 | Not responding | 3 / 191 |
| 51938 | Not responding | 3 / 240 |
| 62314 | Not responding | 3 / 229 |
| 63790 | Not responding | 3 / 231 |
| 22354 | Not responding | 2 / 235 |
| 30391 | Not responding | 2 / 227 |
| 52203 | Not responding | 2 / 236 |
| 52828 | Not responding | 2 / 247 |
| 53078 | Not responding | 2 / 227 |
| 53281 | Not responding | 2 / 243 |
| 56870 | Not responding | 2 / 230 |
| 8865 | Not responding | 1 / 245 |
| 8880 | Not responding | 1 / 239 |
| 9443 | Not responding | 1 / 27 |
| 9991 | Not responding | 1 / 244 |
| 34177 | Not responding | 1 / 236 |
| 37234 | Not responding | 1 / 241 |
| 56561 | Not responding | 1 / 233 |
| 56732 | Not responding | 1 / 238 |
| 63768 | Not responding | 1 / 232 |
| 8112 | Not responding | 0 / 222 |
| 32945 | Not responding | 0 / 26 |
| 34409 | Not responding | 0 / 26 |
| 36361 | Not responding | 0 / 26 |
| 38131 | Not responding | 0 / 26 |
| 38583 | Not responding | 0 / 26 |
| 50249 | Not responding | 0 / 180 |
| 51611 | Not responding | 0 / 198 |
| 62761 | Not responding | 0 / 178 |
| 63234 | Not responding | 0 / 26 |
Questions about 174.138.162.238
Is 174.138.162.238 a proxy?
Not at this moment, but it has been. 79 of the 89 ports we track on 174.138.162.238 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.162.238 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.162.238?
Since May 13, 2026. We have run 23,958 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 →
173.212.203.209:80
HTTP · France · 100% · 5ms
3.121.130.230:1088
HTTP · Germany · 15% · 10ms
18.185.103.130:443
HTTP · Germany · 99% · 13ms
63.181.83.210:9394
HTTP · Germany · 14% · 13ms
37.120.189.106:80
HTTP · Germany · 98% · 14ms
47.91.65.12:80
HTTP · Germany · 100% · 15ms
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.