Is 174.138.161.174 a proxy? Yes, it was.

174.138.161.174 has been a working public proxy: 70 of the 122 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
122

ports recorded on this address

Answering now0
Ever answered70
Checks run9,929
First recorded2026-05-20

Ports recorded on 174.138.161.174

We hold 122 ports on 174.138.161.174 and have run 9,929 checks against them. 70 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.174, with how many checks each has answered
PortStatusTimes answered
8092Not responding20 / 91
58300Not responding5 / 93
31920Not responding4 / 92
32376Not responding4 / 90
33507Not responding4 / 91
63885Not responding4 / 87
32695Not responding3 / 88
34249Not responding3 / 85
50293Not responding3 / 91
53623Not responding3 / 80
55931Not responding3 / 89
20573Not responding2 / 91
30442Not responding2 / 74
31226Not responding2 / 83
Show the other 108 ports on this page
The remaining ports HProxy has recorded on 174.138.161.174
PortStatusTimes answered
31375Not responding2 / 94
32579Not responding2 / 90
32650Not responding2 / 86
33238Not responding2 / 89
33292Not responding2 / 86
33463Not responding2 / 92
50550Not responding2 / 89
55126Not responding2 / 85
56448Not responding2 / 87
58069Not responding2 / 86
65036Not responding2 / 69
8080Not responding1 / 92
8081Not responding1 / 88
8118Not responding1 / 85
8129Not responding1 / 80
8734Not responding1 / 85
20012Not responding1 / 70
20059Not responding1 / 85
22311Not responding1 / 85
22903Not responding1 / 83
30381Not responding1 / 72
30427Not responding1 / 90
30701Not responding1 / 85
31475Not responding1 / 89
31994Not responding1 / 70
32005Not responding1 / 76
32789Not responding1 / 73
33268Not responding1 / 87
34203Not responding1 / 89
34433Not responding1 / 79
34628Not responding1 / 70
35011Not responding1 / 81
35192Not responding1 / 71
35197Not responding1 / 85
35806Not responding1 / 91
36089Not responding1 / 74
37234Not responding1 / 91
37298Not responding1 / 63
37601Not responding1 / 87
37956Not responding1 / 70
38180Not responding1 / 91
39140Not responding1 / 89
40000Not responding1 / 77
50101Not responding1 / 85
50665Not responding1 / 85
51512Not responding1 / 84
52054Not responding1 / 73
52517Not responding1 / 84
52908Not responding1 / 74
55219Not responding1 / 89
55740Not responding1 / 79
55874Not responding1 / 75
56536Not responding1 / 86
57239Not responding1 / 74
58244Not responding1 / 76
59392Not responding1 / 91
8763Not responding0 / 84
8889Not responding0 / 76
9119Not responding0 / 91
9409Not responding0 / 86
20078Not responding0 / 71
23226Not responding0 / 85
25401Not responding0 / 90
26591Not responding0 / 89
30212Not responding0 / 86
30691Not responding0 / 89
31074Not responding0 / 75
32654Not responding0 / 90
32868Not responding0 / 69
33208Not responding0 / 67
33839Not responding0 / 79
33985Not responding0 / 67
34596Not responding0 / 86
34883Not responding0 / 90
35708Not responding0 / 63
36176Not responding0 / 78
36206Not responding0 / 81
36432Not responding0 / 70
36594Not responding0 / 75
37024Not responding0 / 88
37586Not responding0 / 69
37716Not responding0 / 80
37947Not responding0 / 86
38259Not responding0 / 66
38402Not responding0 / 75
39316Not responding0 / 87
50059Not responding0 / 77
50735Not responding0 / 76
51523Not responding0 / 88
51524Not responding0 / 87
51539Not responding0 / 87
52437Not responding0 / 71
52686Not responding0 / 68
52810Not responding0 / 31
53085Not responding0 / 68
53088Not responding0 / 67
53227Not responding0 / 87
53281Not responding0 / 93
54042Not responding0 / 81
54260Not responding0 / 90
54343Not responding0 / 81
54559Not responding0 / 92
55100Not responding0 / 66
55586Not responding0 / 87
56820Not responding0 / 81
57237Not responding0 / 65
58025Not responding0 / 74
58104Not responding0 / 88

Questions about 174.138.161.174

Is 174.138.161.174 a proxy?

Not at this moment, but it has been. 70 of the 122 ports we track on 174.138.161.174 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.174 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.174?

Since May 20, 2026. We have run 9,929 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 free→Compare 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.