Is 174.138.163.52 a proxy? Yes, it was.

174.138.163.52 has been a working public proxy: 77 of the 117 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
117

ports recorded on this address

Answering now0
Ever answered77
Checks run19,226
First recorded2026-05-13

Ports recorded on 174.138.163.52

We hold 117 ports on 174.138.163.52 and have run 19,226 checks against them. 77 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.52, with how many checks each has answered
PortStatusTimes answered
8001Not responding15 / 247
8003Not responding6 / 234
55368Not responding5 / 244
62463Not responding5 / 244
35089Not responding4 / 239
35701Not responding4 / 239
52022Not responding4 / 243
37729Not responding3 / 239
37919Not responding3 / 236
38055Not responding3 / 239
39387Not responding3 / 236
51730Not responding3 / 238
53238Not responding3 / 232
53618Not responding3 / 245
Show the other 103 ports on this page
The remaining ports HProxy has recorded on 174.138.163.52
PortStatusTimes answered
8738Not responding2 / 231
22630Not responding2 / 236
26704Not responding2 / 229
30095Not responding2 / 237
30559Not responding2 / 243
30630Not responding2 / 233
33246Not responding2 / 243
36802Not responding2 / 247
37254Not responding2 / 241
37606Not responding2 / 232
37887Not responding2 / 243
37956Not responding2 / 239
38021Not responding2 / 238
38964Not responding2 / 241
50049Not responding2 / 233
51093Not responding2 / 234
51307Not responding2 / 234
52944Not responding2 / 240
53576Not responding2 / 233
53581Not responding2 / 242
54919Not responding2 / 238
55245Not responding2 / 240
55457Not responding2 / 240
8080Not responding1 / 32
8220Not responding1 / 32
9066Not responding1 / 32
9284Not responding1 / 32
9767Not responding1 / 32
20398Not responding1 / 32
21785Not responding1 / 32
26210Not responding1 / 241
30480Not responding1 / 32
31454Not responding1 / 32
31480Not responding1 / 32
31766Not responding1 / 232
32278Not responding1 / 32
32650Not responding1 / 32
33901Not responding1 / 32
34084Not responding1 / 32
34268Not responding1 / 240
34588Not responding1 / 245
36537Not responding1 / 233
36760Not responding1 / 232
37180Not responding1 / 32
37252Not responding1 / 236
37620Not responding1 / 32
37665Not responding1 / 226
38502Not responding1 / 236
50264Not responding1 / 233
50407Not responding1 / 242
50530Not responding1 / 226
50802Not responding1 / 32
51019Not responding1 / 237
51112Not responding1 / 237
51971Not responding1 / 240
52462Not responding1 / 241
55653Not responding1 / 232
55675Not responding1 / 243
55821Not responding1 / 32
56268Not responding1 / 32
56886Not responding1 / 243
63375Not responding1 / 32
65242Not responding1 / 32
8181Not responding0 / 223
8821Not responding0 / 30
8888Not responding0 / 29
9553Not responding0 / 29
9842Not responding0 / 235
21177Not responding0 / 29
21189Not responding0 / 29
30118Not responding0 / 29
30371Not responding0 / 29
30566Not responding0 / 234
30820Not responding0 / 222
31633Not responding0 / 29
32583Not responding0 / 29
32952Not responding0 / 29
33352Not responding0 / 240
33756Not responding0 / 242
34033Not responding0 / 222
38586Not responding0 / 30
38724Not responding0 / 236
38741Not responding0 / 230
50695Not responding0 / 244
50721Not responding0 / 230
51305Not responding0 / 241
51453Not responding0 / 233
51854Not responding0 / 230
52713Not responding0 / 29
54527Not responding0 / 240
55082Not responding0 / 29
55409Not responding0 / 30
55423Not responding0 / 224
55443Not responding0 / 30
55533Not responding0 / 222
56010Not responding0 / 29
56826Not responding0 / 230
57182Not responding0 / 29
57393Not responding0 / 29
57406Not responding0 / 29
59126Not responding0 / 29
59330Not responding0 / 241
65277Not responding0 / 234

Questions about 174.138.163.52

Is 174.138.163.52 a proxy?

Not at this moment, but it has been. 77 of the 117 ports we track on 174.138.163.52 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.52 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.52?

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