Is 174.138.170.54 a proxy? Yes, it was.

174.138.170.54 has been a working public proxy: 86 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 answered86
Checks run3,675
First recorded2026-05-27

Ports recorded on 174.138.170.54

We hold 117 ports on 174.138.170.54 and have run 3,675 checks against them. 86 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.54, with how many checks each has answered
PortStatusTimes answered
8024Not responding1 / 32
8080Not responding1 / 32
8192Not responding1 / 32
8230Not responding1 / 32
8254Not responding1 / 32
8509Not responding1 / 32
8850Not responding1 / 32
8878Not responding1 / 32
8938Not responding1 / 32
9190Not responding1 / 32
9307Not responding1 / 32
20051Not responding1 / 32
20152Not responding1 / 32
20455Not responding1 / 32
Show the other 103 ports on this page
The remaining ports HProxy has recorded on 174.138.170.54
PortStatusTimes answered
20638Not responding1 / 32
26575Not responding1 / 32
30055Not responding1 / 32
30879Not responding1 / 32
30980Not responding1 / 32
31437Not responding1 / 32
31496Not responding1 / 32
31631Not responding1 / 32
31735Not responding1 / 32
31998Not responding1 / 32
32099Not responding1 / 32
32595Not responding1 / 32
32703Not responding1 / 32
32731Not responding1 / 32
32975Not responding1 / 32
33330Not responding1 / 32
33366Not responding1 / 32
33890Not responding1 / 32
34193Not responding1 / 32
34253Not responding1 / 32
34593Not responding1 / 32
34810Not responding1 / 32
34896Not responding1 / 32
35511Not responding1 / 32
36359Not responding1 / 32
36389Not responding1 / 32
36440Not responding1 / 32
36578Not responding1 / 32
36744Not responding1 / 32
37234Not responding1 / 32
37493Not responding1 / 32
37501Not responding1 / 32
37672Not responding1 / 32
37759Not responding1 / 32
37804Not responding1 / 32
38171Not responding1 / 32
38290Not responding1 / 32
38298Not responding1 / 32
39605Not responding1 / 32
50350Not responding1 / 32
50917Not responding1 / 32
51091Not responding1 / 32
51307Not responding1 / 32
51497Not responding1 / 32
51726Not responding1 / 32
52061Not responding1 / 32
52147Not responding1 / 32
52384Not responding1 / 32
53107Not responding1 / 32
53523Not responding1 / 32
53660Not responding1 / 32
53899Not responding1 / 32
54153Not responding1 / 32
54308Not responding1 / 32
54466Not responding1 / 32
54679Not responding1 / 32
54868Not responding1 / 32
54900Not responding1 / 32
55082Not responding1 / 32
55087Not responding1 / 32
55155Not responding1 / 32
55349Not responding1 / 32
55410Not responding1 / 32
55714Not responding1 / 32
55754Not responding1 / 32
55885Not responding1 / 32
56268Not responding1 / 32
56619Not responding1 / 32
56869Not responding1 / 32
57094Not responding1 / 32
62320Not responding1 / 32
63036Not responding1 / 32
8009Not responding0 / 30
20106Not responding0 / 30
30891Not responding0 / 30
31070Not responding0 / 29
31375Not responding0 / 30
31480Not responding0 / 30
32650Not responding0 / 29
33754Not responding0 / 30
34510Not responding0 / 29
35956Not responding0 / 30
38482Not responding0 / 30
38989Not responding0 / 29
39867Not responding0 / 29
39953Not responding0 / 30
39980Not responding0 / 30
50913Not responding0 / 30
51135Not responding0 / 30
51577Not responding0 / 30
52686Not responding0 / 30
53246Not responding0 / 30
54359Not responding0 / 30
54544Not responding0 / 30
54756Not responding0 / 30
55851Not responding0 / 30
55924Not responding0 / 30
55966Not responding0 / 29
56679Not responding0 / 30
56799Not responding0 / 30
56917Not responding0 / 30
57725Not responding0 / 30
62994Not responding0 / 29

Questions about 174.138.170.54

Is 174.138.170.54 a proxy?

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

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