Is 174.138.161.141 a proxy? Yes, it was.

174.138.161.141 has been a working public proxy: 21 of the 49 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
49

ports recorded on this address

Answering now0
Ever answered21
Checks run1,505
First recorded2026-05-27

Ports recorded on 174.138.161.141

We hold 49 ports on 174.138.161.141 and have run 1,505 checks against them. 21 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.141, with how many checks each has answered
PortStatusTimes answered
8009Not responding1 / 32
8080Not responding1 / 32
9903Not responding1 / 32
20329Not responding1 / 32
21499Not responding1 / 32
21754Not responding1 / 32
31858Not responding1 / 32
32455Not responding1 / 32
32827Not responding1 / 32
32934Not responding1 / 32
50873Not responding1 / 32
52257Not responding1 / 32
52398Not responding1 / 32
54000Not responding1 / 32
Show the other 35 ports on this page
The remaining ports HProxy has recorded on 174.138.161.141
PortStatusTimes answered
56607Not responding1 / 32
56818Not responding1 / 32
57685Not responding1 / 32
58052Not responding1 / 32
63369Not responding1 / 32
63474Not responding1 / 32
64918Not responding1 / 32
9050Not responding0 / 30
20084Not responding0 / 30
20207Not responding0 / 30
20548Not responding0 / 30
30194Not responding0 / 30
31705Not responding0 / 30
31914Not responding0 / 30
32650Not responding0 / 30
33949Not responding0 / 29
34737Not responding0 / 30
36077Not responding0 / 30
36388Not responding0 / 30
37026Not responding0 / 30
38300Not responding0 / 30
39345Not responding0 / 30
39910Not responding0 / 30
51200Not responding0 / 29
51626Not responding0 / 29
53867Not responding0 / 29
55910Not responding0 / 30
56817Not responding0 / 30
56869Not responding0 / 30
56889Not responding0 / 30
56914Not responding0 / 30
56990Not responding0 / 29
58276Not responding0 / 30
63171Not responding0 / 29
64947Not responding0 / 29

Questions about 174.138.161.141

Is 174.138.161.141 a proxy?

Not at this moment, but it has been. 21 of the 49 ports we track on 174.138.161.141 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.141 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.141?

Since May 27, 2026. We have run 1,505 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.