Is 174.138.165.203 a proxy? Yes, it was.

174.138.165.203 has been a working public proxy: 83 of the 116 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
116

ports recorded on this address

Answering now0
Ever answered83
Checks run21,125
First recorded2026-05-13

Ports recorded on 174.138.165.203

We hold 116 ports on 174.138.165.203 and have run 21,125 checks against them. 83 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.165.203, with how many checks each has answered
PortStatusTimes answered
8092Not responding23 / 267
8254Not responding22 / 489
8220Not responding19 / 471
30705Not responding17 / 478
30678Not responding12 / 249
39210Not responding12 / 484
9230Not responding10 / 493
39698Not responding9 / 269
37929Not responding8 / 477
8745Not responding7 / 258
32039Not responding6 / 256
53450Not responding6 / 40
8001Not responding5 / 245
8109Not responding5 / 38
Show the other 102 ports on this page
The remaining ports HProxy has recorded on 174.138.165.203
PortStatusTimes answered
35195Not responding5 / 259
38218Not responding5 / 241
31818Not responding4 / 258
32246Not responding4 / 251
33190Not responding4 / 246
33593Not responding4 / 241
52291Not responding4 / 263
54769Not responding4 / 237
65262Not responding4 / 248
8104Not responding3 / 257
9050Not responding3 / 37
30947Not responding3 / 255
31709Not responding3 / 251
32469Not responding3 / 255
32613Not responding3 / 253
34127Not responding3 / 35
35647Not responding3 / 38
36021Not responding3 / 251
37515Not responding3 / 256
52512Not responding3 / 36
55714Not responding3 / 36
56053Not responding3 / 36
56936Not responding3 / 34
58009Not responding3 / 244
62299Not responding3 / 36
65110Not responding3 / 234
8184Not responding2 / 241
21192Not responding2 / 36
30764Not responding2 / 240
31266Not responding2 / 247
31815Not responding2 / 255
33870Not responding2 / 35
36562Not responding2 / 36
51987Not responding2 / 251
56592Not responding2 / 36
56918Not responding2 / 254
63297Not responding2 / 253
63354Not responding2 / 249
8689Not responding1 / 32
8888Not responding1 / 33
30654Not responding1 / 246
31451Not responding1 / 32
31901Not responding1 / 237
33599Not responding1 / 246
35682Not responding1 / 239
36458Not responding1 / 253
37971Not responding1 / 252
50017Not responding1 / 241
50136Not responding1 / 248
50278Not responding1 / 250
50604Not responding1 / 248
50994Not responding1 / 246
51470Not responding1 / 249
51505Not responding1 / 251
51742Not responding1 / 240
51900Not responding1 / 251
52223Not responding1 / 32
52825Not responding1 / 249
52959Not responding1 / 251
53281Not responding1 / 256
54154Not responding1 / 32
54548Not responding1 / 247
54736Not responding1 / 34
56403Not responding1 / 32
58035Not responding1 / 32
62138Not responding1 / 254
62504Not responding1 / 32
63471Not responding1 / 249
65177Not responding1 / 247
8040Not responding0 / 244
8684Not responding0 / 30
8922Not responding0 / 30
20093Not responding0 / 30
21790Not responding0 / 30
22105Not responding0 / 29
32439Not responding0 / 29
33628Not responding0 / 243
33871Not responding0 / 30
34366Not responding0 / 234
34439Not responding0 / 238
35519Not responding0 / 235
36442Not responding0 / 246
38809Not responding0 / 29
50307Not responding0 / 236
50405Not responding0 / 29
51170Not responding0 / 250
52456Not responding0 / 29
52596Not responding0 / 248
53457Not responding0 / 30
54272Not responding0 / 30
54456Not responding0 / 244
55013Not responding0 / 29
56807Not responding0 / 30
57166Not responding0 / 29
57237Not responding0 / 241
57545Not responding0 / 30
57734Not responding0 / 245
62328Not responding0 / 247
62472Not responding0 / 30
64917Not responding0 / 30
65148Not responding0 / 235
65359Not responding0 / 30

Questions about 174.138.165.203

Is 174.138.165.203 a proxy?

Not at this moment, but it has been. 83 of the 116 ports we track on 174.138.165.203 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.165.203 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.165.203?

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