Is 174.138.161.220 a proxy? Yes, it was.

174.138.161.220 has been a working public proxy: 39 of the 50 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.

Not responding
50

ports recorded on this address

Answering now0
Ever answered39
Checks run11,532
First recorded2026-05-13

Ports recorded on 174.138.161.220

We hold 50 ports on 174.138.161.220 and have run 11,532 checks against them. 39 ports have answered at some point, though none are answering right now. Open any port for its full record.

Every port HProxy has recorded on 174.138.161.220, with how many checks each has answered
PortStatusTimes answered
8001Not responding34 / 245
52976Not responding7 / 239
30286Not responding4 / 232
38836Not responding4 / 241
55603Not responding4 / 229
8254Not responding3 / 186
30851Not responding3 / 232
31005Not responding3 / 232
31078Not responding3 / 240
32125Not responding3 / 240
34151Not responding3 / 232
51413Not responding3 / 235
51971Not responding3 / 234
54513Not responding3 / 237
Show the other 36 ports on this page
The remaining ports HProxy has recorded on 174.138.161.220
PortStatusTimes answered
55172Not responding3 / 237
62223Not responding3 / 236
8750Not responding2 / 215
9108Not responding2 / 239
30811Not responding2 / 236
38964Not responding2 / 242
39162Not responding2 / 244
50613Not responding2 / 232
50918Not responding2 / 238
51874Not responding2 / 234
54285Not responding2 / 235
55897Not responding2 / 230
56963Not responding2 / 241
59165Not responding2 / 235
8220Not responding1 / 203
8865Not responding1 / 233
31061Not responding1 / 241
35301Not responding1 / 238
37441Not responding1 / 234
39142Not responding1 / 243
39313Not responding1 / 241
51368Not responding1 / 232
53450Not responding1 / 230
53488Not responding1 / 224
53826Not responding1 / 231
8202Not responding0 / 191
20654Not responding0 / 223
21623Not responding0 / 235
22343Not responding0 / 235
30085Not responding0 / 233
33246Not responding0 / 221
39242Not responding0 / 234
39481Not responding0 / 232
50339Not responding0 / 231
56638Not responding0 / 221
56725Not responding0 / 178

Questions about 174.138.161.220

Is 174.138.161.220 a proxy?

Not at this moment, but it has been. 39 of the 50 ports we track on 174.138.161.220 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.161.220 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.161.220?

Since May 13, 2026. We have run 11,532 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.

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.

Clean residential poolsCity-level targetingSticky sessions up to 24 h

Starting from

$0.44/GB

Billed per GB · balance never expires

Get started freeCompare plans & pricing
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.