Is 174.138.165.212 a proxy? Yes, it was.

174.138.165.212 has been a working public proxy: 41 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 answered41
Checks run3,367
First recorded2026-05-16

Ports recorded on 174.138.165.212

We hold 105 ports on 174.138.165.212 and have run 3,367 checks against them. 41 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.212, with how many checks each has answered
PortStatusTimes answered
8170Not responding1 / 32
8250Not responding1 / 32
8914Not responding1 / 32
9428Not responding1 / 32
9627Not responding1 / 32
30004Not responding1 / 32
30253Not responding1 / 32
30436Not responding1 / 32
30479Not responding1 / 32
30594Not responding1 / 32
33115Not responding1 / 32
33212Not responding1 / 32
33802Not responding1 / 32
33816Not responding1 / 32
Show the other 91 ports on this page
The remaining ports HProxy has recorded on 174.138.165.212
PortStatusTimes answered
33895Not responding1 / 32
34971Not responding1 / 32
35178Not responding1 / 32
35647Not responding1 / 32
36544Not responding1 / 32
36758Not responding1 / 32
37304Not responding1 / 32
37554Not responding1 / 32
37794Not responding1 / 32
38205Not responding1 / 32
39911Not responding1 / 32
50123Not responding1 / 32
50236Not responding1 / 32
50623Not responding1 / 32
50985Not responding1 / 32
51227Not responding1 / 32
53680Not responding1 / 32
55606Not responding1 / 32
55942Not responding1 / 32
56010Not responding1 / 32
56265Not responding1 / 32
56620Not responding1 / 32
56686Not responding1 / 32
59938Not responding1 / 32
62611Not responding1 / 32
63800Not responding1 / 32
65352Not responding1 / 32
8009Not responding0 / 29
8865Not responding0 / 30
9063Not responding0 / 30
9399Not responding0 / 30
30181Not responding0 / 30
30860Not responding0 / 29
31137Not responding0 / 30
31191Not responding0 / 30
31296Not responding0 / 30
31488Not responding0 / 30
31930Not responding0 / 29
32043Not responding0 / 30
32430Not responding0 / 30
33263Not responding0 / 30
33328Not responding0 / 30
33870Not responding0 / 29
34230Not responding0 / 30
34357Not responding0 / 30
34878Not responding0 / 30
35539Not responding0 / 30
35562Not responding0 / 30
36028Not responding0 / 30
36431Not responding0 / 30
36524Not responding0 / 30
36896Not responding0 / 30
37234Not responding0 / 30
37462Not responding0 / 30
37514Not responding0 / 30
38164Not responding0 / 178
38521Not responding0 / 29
38677Not responding0 / 30
38947Not responding0 / 30
50056Not responding0 / 30
50080Not responding0 / 29
50528Not responding0 / 30
50606Not responding0 / 30
50840Not responding0 / 30
50992Not responding0 / 29
51131Not responding0 / 30
51248Not responding0 / 30
51683Not responding0 / 30
52030Not responding0 / 30
52294Not responding0 / 30
52446Not responding0 / 30
52743Not responding0 / 30
53281Not responding0 / 30
54079Not responding0 / 30
54204Not responding0 / 29
54308Not responding0 / 29
54787Not responding0 / 30
55091Not responding0 / 30
55714Not responding0 / 29
55840Not responding0 / 30
55969Not responding0 / 29
56320Not responding0 / 30
56571Not responding0 / 29
56708Not responding0 / 29
56891Not responding0 / 30
57122Not responding0 / 30
57431Not responding0 / 30
58090Not responding0 / 30
62722Not responding0 / 30
63651Not responding0 / 30
65444Not responding0 / 30

Questions about 174.138.165.212

Is 174.138.165.212 a proxy?

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

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

Is 174.138.165.212 a proxy? 41 of 105 ports worked | HProxy