Is 174.138.162.252 a proxy? Yes, it was.

174.138.162.252 has been a working public proxy: 41 of the 50 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
50

ports recorded on this address

Answering now0
Ever answered41
Checks run13,053
First recorded2026-05-13

Ports recorded on 174.138.162.252

We hold 50 ports on 174.138.162.252 and have run 13,053 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.162.252, with how many checks each has answered
PortStatusTimes answered
8254Not responding25 / 475
56958Not responding20 / 480
31371Not responding19 / 480
30673Not responding17 / 250
31826Not responding16 / 463
53575Not responding16 / 468
54336Not responding16 / 480
9991Not responding13 / 251
38091Not responding12 / 248
9075Not responding11 / 247
34907Not responding11 / 478
38479Not responding11 / 248
52720Not responding11 / 243
63152Not responding11 / 247
Show the other 36 ports on this page
The remaining ports HProxy has recorded on 174.138.162.252
PortStatusTimes answered
30302Not responding10 / 457
56353Not responding9 / 240
9247Not responding7 / 244
39142Not responding7 / 244
55849Not responding7 / 246
30789Not responding6 / 251
32764Not responding6 / 241
34204Not responding6 / 241
36169Not responding6 / 242
32649Not responding5 / 248
56065Not responding5 / 453
36764Not responding4 / 247
37234Not responding4 / 250
37602Not responding4 / 443
38724Not responding4 / 241
51274Not responding4 / 448
9404Not responding3 / 447
54135Not responding3 / 235
38964Not responding2 / 241
51222Not responding2 / 247
21928Not responding1 / 240
24049Not responding1 / 237
30860Not responding1 / 227
31291Not responding1 / 238
37620Not responding1 / 241
55037Not responding1 / 235
55494Not responding1 / 237
8001Not responding0 / 24
8181Not responding0 / 25
8889Not responding0 / 26
21682Not responding0 / 26
38945Not responding0 / 26
50160Not responding0 / 231
53545Not responding0 / 26
55671Not responding0 / 25
59799Not responding0 / 25

Questions about 174.138.162.252

Is 174.138.162.252 a proxy?

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

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