Is 174.138.163.50 a proxy? Yes, it was.

174.138.163.50 has been a working public proxy: 59 of the 105 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
105

ports recorded on this address

Answering now0
Ever answered59
Checks run12,780
First recorded2026-05-13

Ports recorded on 174.138.163.50

We hold 105 ports on 174.138.163.50 and have run 12,780 checks against them. 59 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.163.50, with how many checks each has answered
PortStatusTimes answered
8001Not responding19 / 245
58163Not responding6 / 241
8202Not responding4 / 227
37521Not responding4 / 233
31401Not responding3 / 240
33504Not responding3 / 237
53338Not responding3 / 237
55612Not responding3 / 239
8220Not responding2 / 33
8530Not responding2 / 244
31958Not responding2 / 238
32506Not responding2 / 238
37514Not responding2 / 240
39583Not responding2 / 243
Show the other 91 ports on this page
The remaining ports HProxy has recorded on 174.138.163.50
PortStatusTimes answered
50954Not responding2 / 238
53235Not responding2 / 237
55030Not responding2 / 235
55802Not responding2 / 238
8230Not responding1 / 32
8250Not responding1 / 32
8254Not responding1 / 32
8849Not responding1 / 234
8896Not responding1 / 32
9402Not responding1 / 32
22854Not responding1 / 222
30705Not responding1 / 32
30919Not responding1 / 244
30959Not responding1 / 32
31631Not responding1 / 32
33023Not responding1 / 32
33738Not responding1 / 32
33831Not responding1 / 32
34131Not responding1 / 228
38111Not responding1 / 237
39032Not responding1 / 32
39103Not responding1 / 232
50202Not responding1 / 232
50803Not responding1 / 229
51551Not responding1 / 32
51960Not responding1 / 32
52686Not responding1 / 32
52920Not responding1 / 236
53059Not responding1 / 32
53146Not responding1 / 230
53195Not responding1 / 237
53480Not responding1 / 32
53793Not responding1 / 234
54194Not responding1 / 32
54635Not responding1 / 32
54865Not responding1 / 32
55485Not responding1 / 32
56001Not responding1 / 247
56693Not responding1 / 32
56936Not responding1 / 32
57316Not responding1 / 32
57688Not responding1 / 32
59837Not responding1 / 32
63530Not responding1 / 32
65178Not responding1 / 32
8718Not responding0 / 29
8821Not responding0 / 29
9050Not responding0 / 234
9664Not responding0 / 234
9917Not responding0 / 29
20317Not responding0 / 30
20582Not responding0 / 29
20867Not responding0 / 29
21711Not responding0 / 237
22853Not responding0 / 220
31454Not responding0 / 30
31714Not responding0 / 235
32344Not responding0 / 29
32533Not responding0 / 236
32614Not responding0 / 30
32650Not responding0 / 29
33428Not responding0 / 29
33600Not responding0 / 230
34242Not responding0 / 29
34536Not responding0 / 30
35574Not responding0 / 29
35789Not responding0 / 237
35914Not responding0 / 222
36124Not responding0 / 220
36406Not responding0 / 30
36521Not responding0 / 29
36578Not responding0 / 29
37339Not responding0 / 29
37771Not responding0 / 29
38505Not responding0 / 229
38770Not responding0 / 30
39378Not responding0 / 233
50010Not responding0 / 230
50177Not responding0 / 29
50890Not responding0 / 220
51111Not responding0 / 222
52258Not responding0 / 29
52865Not responding0 / 29
54058Not responding0 / 237
54431Not responding0 / 29
54565Not responding0 / 29
57226Not responding0 / 29
57389Not responding0 / 30
59548Not responding0 / 29
63168Not responding0 / 30
65473Not responding0 / 234

Questions about 174.138.163.50

Is 174.138.163.50 a proxy?

Not at this moment, but it has been. 59 of the 105 ports we track on 174.138.163.50 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.163.50 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.163.50?

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