Is 174.138.170.52 a proxy? Yes, it was.

174.138.170.52 has been a working public proxy: 81 of the 112 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
112

ports recorded on this address

Answering now0
Ever answered81
Checks run3,509
First recorded2026-05-27

Ports recorded on 174.138.170.52

We hold 112 ports on 174.138.170.52 and have run 3,509 checks against them. 81 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.170.52, with how many checks each has answered
PortStatusTimes answered
8001Not responding1 / 32
8149Not responding1 / 32
8192Not responding1 / 32
8715Not responding1 / 32
8770Not responding1 / 32
8789Not responding1 / 32
8850Not responding1 / 32
8879Not responding1 / 32
8888Not responding1 / 32
8907Not responding1 / 32
9555Not responding1 / 32
9824Not responding1 / 32
20159Not responding1 / 32
21074Not responding1 / 32
Show the other 98 ports on this page
The remaining ports HProxy has recorded on 174.138.170.52
PortStatusTimes answered
31125Not responding1 / 32
31270Not responding1 / 32
31302Not responding1 / 32
31738Not responding1 / 32
32140Not responding1 / 32
32290Not responding1 / 32
32424Not responding1 / 32
32439Not responding1 / 32
32569Not responding1 / 32
32614Not responding1 / 32
32680Not responding1 / 32
32941Not responding1 / 32
33154Not responding1 / 32
33333Not responding1 / 32
33428Not responding1 / 32
33545Not responding1 / 32
33661Not responding1 / 32
33874Not responding1 / 32
33935Not responding1 / 32
34752Not responding1 / 32
35038Not responding1 / 32
35539Not responding1 / 32
36026Not responding1 / 32
36158Not responding1 / 32
36357Not responding1 / 32
36674Not responding1 / 32
37501Not responding1 / 32
37570Not responding1 / 32
38201Not responding1 / 32
38274Not responding1 / 32
38398Not responding1 / 32
39184Not responding1 / 32
39298Not responding1 / 32
39909Not responding1 / 32
50415Not responding1 / 32
50537Not responding1 / 32
50776Not responding1 / 32
50788Not responding1 / 32
50791Not responding1 / 32
51107Not responding1 / 32
51804Not responding1 / 32
52160Not responding1 / 32
52541Not responding1 / 32
52584Not responding1 / 32
53252Not responding1 / 32
53281Not responding1 / 32
53558Not responding1 / 32
54090Not responding1 / 32
54901Not responding1 / 32
54996Not responding1 / 32
55222Not responding1 / 32
55548Not responding1 / 32
55575Not responding1 / 32
55910Not responding1 / 32
56461Not responding1 / 32
56470Not responding1 / 32
56890Not responding1 / 32
57005Not responding1 / 32
57013Not responding1 / 32
57109Not responding1 / 32
57218Not responding1 / 32
57382Not responding1 / 32
57519Not responding1 / 32
59748Not responding1 / 32
62891Not responding1 / 32
65074Not responding1 / 32
65449Not responding1 / 32
8021Not responding0 / 30
8530Not responding0 / 30
23977Not responding0 / 30
30009Not responding0 / 30
30037Not responding0 / 29
31057Not responding0 / 29
31218Not responding0 / 30
31230Not responding0 / 30
31521Not responding0 / 29
32650Not responding0 / 29
33493Not responding0 / 30
33568Not responding0 / 30
34238Not responding0 / 30
34443Not responding0 / 29
36961Not responding0 / 29
37030Not responding0 / 29
37535Not responding0 / 30
39944Not responding0 / 30
51206Not responding0 / 29
51549Not responding0 / 30
52487Not responding0 / 30
52570Not responding0 / 29
52801Not responding0 / 29
53528Not responding0 / 29
53805Not responding0 / 30
55684Not responding0 / 30
56153Not responding0 / 30
56450Not responding0 / 29
56838Not responding0 / 30
57607Not responding0 / 30
63849Not responding0 / 29

Questions about 174.138.170.52

Is 174.138.170.52 a proxy?

Not at this moment, but it has been. 81 of the 112 ports we track on 174.138.170.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.170.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.170.52?

Since May 27, 2026. We have run 3,509 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.