Is 174.138.162.204 a proxy? Yes, it was.

174.138.162.204 has been a working public proxy: 66 of the 103 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
103

ports recorded on this address

Answering now0
Ever answered66
Checks run13,216
First recorded2026-05-13

Ports recorded on 174.138.162.204

We hold 103 ports on 174.138.162.204 and have run 13,216 checks against them. 66 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.162.204, with how many checks each has answered
PortStatusTimes answered
8001Not responding15 / 254
54271Not responding11 / 258
52063Not responding8 / 242
30435Not responding7 / 249
50868Not responding6 / 241
50350Not responding5 / 239
8092Not responding4 / 249
37011Not responding4 / 239
38964Not responding4 / 237
39849Not responding4 / 245
8892Not responding3 / 246
30184Not responding3 / 247
33804Not responding3 / 240
36081Not responding3 / 248
Show the other 89 ports on this page
The remaining ports HProxy has recorded on 174.138.162.204
PortStatusTimes answered
38169Not responding3 / 239
56229Not responding3 / 245
21471Not responding2 / 235
32993Not responding2 / 246
33108Not responding2 / 243
35585Not responding2 / 239
35819Not responding2 / 239
38106Not responding2 / 243
50797Not responding2 / 236
54212Not responding2 / 244
8043Not responding1 / 32
8080Not responding1 / 33
8109Not responding1 / 31
8142Not responding1 / 32
8220Not responding1 / 32
8509Not responding1 / 32
9443Not responding1 / 244
9597Not responding1 / 237
20495Not responding1 / 32
20912Not responding1 / 235
21454Not responding1 / 237
26455Not responding1 / 32
32975Not responding1 / 32
33238Not responding1 / 32
33364Not responding1 / 32
33396Not responding1 / 32
33582Not responding1 / 32
33843Not responding1 / 32
34127Not responding1 / 32
34711Not responding1 / 236
34907Not responding1 / 32
38381Not responding1 / 32
38512Not responding1 / 246
39862Not responding1 / 232
50139Not responding1 / 32
50339Not responding1 / 232
50723Not responding1 / 32
50789Not responding1 / 32
51481Not responding1 / 233
52090Not responding1 / 32
53235Not responding1 / 238
53433Not responding1 / 239
54155Not responding1 / 32
55659Not responding1 / 32
55704Not responding1 / 240
56010Not responding1 / 30
56668Not responding1 / 231
56755Not responding1 / 32
57615Not responding1 / 32
62761Not responding1 / 241
65191Not responding1 / 32
65300Not responding1 / 234
8034Not responding0 / 30
8104Not responding0 / 243
8530Not responding0 / 29
8803Not responding0 / 29
8821Not responding0 / 29
20144Not responding0 / 29
30220Not responding0 / 29
30929Not responding0 / 29
31461Not responding0 / 30
32290Not responding0 / 30
32358Not responding0 / 29
32677Not responding0 / 30
34585Not responding0 / 29
35665Not responding0 / 29
36578Not responding0 / 30
36722Not responding0 / 232
36985Not responding0 / 240
37234Not responding0 / 241
37891Not responding0 / 30
38931Not responding0 / 237
39269Not responding0 / 233
50805Not responding0 / 29
51171Not responding0 / 30
51578Not responding0 / 30
51698Not responding0 / 30
51812Not responding0 / 29
53281Not responding0 / 233
53406Not responding0 / 233
54018Not responding0 / 29
54218Not responding0 / 241
54796Not responding0 / 30
55470Not responding0 / 29
55931Not responding0 / 30
56085Not responding0 / 29
56808Not responding0 / 29
56950Not responding0 / 29
63149Not responding0 / 29

Questions about 174.138.162.204

Is 174.138.162.204 a proxy?

Not at this moment, but it has been. 66 of the 103 ports we track on 174.138.162.204 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.204 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.204?

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