Is 174.138.162.37 a proxy? Yes, it was.

174.138.162.37 has been a working public proxy: 49 of the 53 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
53

ports recorded on this address

Answering now0
Ever answered49
Checks run12,076
First recorded2026-05-13

Ports recorded on 174.138.162.37

We hold 53 ports on 174.138.162.37 and have run 12,076 checks against them. 49 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.162.37, with how many checks each has answered
PortStatusTimes answered
8001Not responding29 / 244
8080Not responding15 / 244
54343Not responding7 / 233
8760Not responding6 / 227
9787Not responding6 / 230
27122Not responding6 / 222
37426Not responding6 / 224
37624Not responding6 / 231
51049Not responding6 / 225
54461Not responding6 / 225
55450Not responding6 / 208
55592Not responding6 / 223
30685Not responding5 / 208
34775Not responding5 / 218
Show the other 39 ports on this page
The remaining ports HProxy has recorded on 174.138.162.37
PortStatusTimes answered
36055Not responding5 / 233
37212Not responding5 / 236
38036Not responding5 / 208
51961Not responding5 / 231
53000Not responding5 / 236
30622Not responding4 / 205
30764Not responding4 / 234
36019Not responding4 / 205
50222Not responding4 / 237
51813Not responding4 / 235
52818Not responding4 / 231
55956Not responding4 / 237
8697Not responding3 / 227
8865Not responding3 / 235
33246Not responding3 / 237
36093Not responding3 / 221
37234Not responding3 / 236
38020Not responding3 / 238
38724Not responding3 / 234
52724Not responding3 / 220
55303Not responding3 / 233
55588Not responding3 / 208
62918Not responding3 / 232
29191Not responding2 / 235
29555Not responding2 / 229
37184Not responding2 / 195
38221Not responding2 / 229
38710Not responding2 / 232
53640Not responding2 / 237
30328Not responding1 / 232
33135Not responding1 / 233
36497Not responding1 / 239
38113Not responding1 / 234
50460Not responding1 / 221
55443Not responding1 / 225
38802Not responding0 / 230
39446Not responding0 / 232
51041Not responding0 / 232
52909Not responding0 / 230

Questions about 174.138.162.37

Is 174.138.162.37 a proxy?

Not at this moment, but it has been. 49 of the 53 ports we track on 174.138.162.37 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.162.37 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.162.37?

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