Is 174.138.162.242 a proxy? Yes, it was.

174.138.162.242 has been a working public proxy: 54 of the 101 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
101

ports recorded on this address

Answering now0
Ever answered54
Checks run9,803
First recorded2026-06-14

Ports recorded on 174.138.162.242

We hold 101 ports on 174.138.162.242 and have run 9,803 checks against them. 54 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.242, with how many checks each has answered
PortStatusTimes answered
8013Not responding32 / 269
8109Not responding15 / 251
65176Not responding13 / 260
39934Not responding12 / 255
20273Not responding11 / 265
31002Not responding11 / 255
31014Not responding11 / 259
38850Not responding11 / 264
65496Not responding11 / 243
31095Not responding10 / 261
31856Not responding10 / 241
51542Not responding10 / 243
62587Not responding10 / 252
55206Not responding9 / 259
Show the other 87 ports on this page
The remaining ports HProxy has recorded on 174.138.162.242
PortStatusTimes answered
20172Not responding8 / 247
31860Not responding8 / 260
38131Not responding8 / 242
55447Not responding7 / 260
63293Not responding7 / 257
8080Not responding6 / 39
54505Not responding6 / 242
64928Not responding6 / 251
31370Not responding5 / 263
36823Not responding5 / 246
8855Not responding4 / 246
34357Not responding4 / 241
51727Not responding4 / 254
56405Not responding4 / 34
20665Not responding3 / 228
38626Not responding3 / 237
50161Not responding3 / 232
63302Not responding3 / 239
30692Not responding2 / 28
31861Not responding2 / 31
34878Not responding2 / 29
38243Not responding2 / 29
50098Not responding2 / 30
8062Not responding1 / 29
8888Not responding1 / 30
9050Not responding1 / 29
9061Not responding1 / 27
30168Not responding1 / 29
33241Not responding1 / 27
34064Not responding1 / 27
36210Not responding1 / 27
36434Not responding1 / 27
36596Not responding1 / 230
38996Not responding1 / 30
52076Not responding1 / 28
52860Not responding1 / 229
55963Not responding1 / 30
57392Not responding1 / 30
57655Not responding1 / 30
63738Not responding1 / 31
8081Not responding0 / 26
8118Not responding0 / 26
8254Not responding0 / 24
9049Not responding0 / 26
9440Not responding0 / 26
9443Not responding0 / 26
9656Not responding0 / 26
9941Not responding0 / 25
10000Not responding0 / 25
20048Not responding0 / 26
20458Not responding0 / 26
20983Not responding0 / 25
21034Not responding0 / 26
21191Not responding0 / 25
30533Not responding0 / 26
30780Not responding0 / 19
30868Not responding0 / 20
31432Not responding0 / 26
31668Not responding0 / 25
33053Not responding0 / 26
33243Not responding0 / 26
35116Not responding0 / 26
36029Not responding0 / 20
36460Not responding0 / 26
36858Not responding0 / 26
38239Not responding0 / 26
38416Not responding0 / 26
38533Not responding0 / 25
38729Not responding0 / 25
39205Not responding0 / 25
50667Not responding0 / 26
51482Not responding0 / 20
51897Not responding0 / 25
52309Not responding0 / 26
52438Not responding0 / 20
52594Not responding0 / 26
53401Not responding0 / 26
54897Not responding0 / 26
55283Not responding0 / 26
55527Not responding0 / 26
55567Not responding0 / 26
55890Not responding0 / 25
56006Not responding0 / 20
56627Not responding0 / 24
57262Not responding0 / 26
58211Not responding0 / 26
62843Not responding0 / 26

Questions about 174.138.162.242

Is 174.138.162.242 a proxy?

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

Since Jun 14, 2026. We have run 9,803 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.