Is 174.138.171.34 a proxy? Yes, it was.

174.138.171.34 has been a working public proxy: 70 of the 103 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
103

ports recorded on this address

Answering now0
Ever answered70
Checks run26,861
First recorded2026-05-28

Ports recorded on 174.138.171.34

We hold 103 ports on 174.138.171.34 and have run 26,861 checks against them. 70 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.171.34, with how many checks each has answered
PortStatusTimes answered
8080Not responding194 / 591
8254Not responding130 / 472
32650Not responding54 / 498
36792Not responding44 / 529
56557Not responding44 / 463
8118Not responding41 / 385
35732Not responding40 / 434
39811Not responding39 / 414
33109Not responding36 / 443
39453Not responding36 / 399
30327Not responding35 / 387
31002Not responding30 / 397
52648Not responding29 / 366
56806Not responding29 / 321
Show the other 89 ports on this page
The remaining ports HProxy has recorded on 174.138.171.34
PortStatusTimes answered
31985Not responding28 / 533
35616Not responding28 / 436
37049Not responding28 / 394
34172Not responding26 / 413
62694Not responding26 / 423
8910Not responding25 / 416
9424Not responding24 / 385
20172Not responding24 / 391
30636Not responding24 / 359
31290Not responding23 / 478
51019Not responding23 / 425
9050Not responding22 / 368
9887Not responding22 / 313
29200Not responding22 / 342
34922Not responding22 / 363
52986Not responding22 / 341
55390Not responding22 / 411
9061Not responding21 / 341
55343Not responding21 / 370
32597Not responding20 / 388
36300Not responding20 / 409
53545Not responding18 / 471
53671Not responding18 / 374
55740Not responding17 / 354
39522Not responding16 / 346
55280Not responding16 / 312
30238Not responding14 / 398
31170Not responding14 / 268
51924Not responding14 / 362
36843Not responding12 / 364
37156Not responding12 / 432
37234Not responding12 / 313
39152Not responding12 / 311
50629Not responding12 / 356
55961Not responding12 / 378
56731Not responding12 / 353
30578Not responding11 / 372
50048Not responding11 / 354
32526Not responding10 / 339
34466Not responding10 / 279
37756Not responding10 / 379
31280Not responding9 / 345
34968Not responding9 / 341
8746Not responding8 / 301
32142Not responding8 / 320
33358Not responding8 / 341
34026Not responding8 / 369
36327Not responding7 / 333
37351Not responding7 / 313
8532Not responding4 / 243
39754Not responding3 / 259
50652Not responding3 / 395
58031Not responding3 / 331
29597Not responding2 / 231
53263Not responding1 / 218
53345Not responding1 / 228
8818Not responding0 / 20
8882Not responding0 / 22
8888Not responding0 / 23
8889Not responding0 / 22
9054Not responding0 / 25
24974Not responding0 / 23
28120Not responding0 / 19
33055Not responding0 / 21
33325Not responding0 / 25
33346Not responding0 / 25
34128Not responding0 / 25
34812Not responding0 / 25
34838Not responding0 / 25
35073Not responding0 / 25
35881Not responding0 / 25
36181Not responding0 / 19
36483Not responding0 / 25
37122Not responding0 / 21
38277Not responding0 / 23
38704Not responding0 / 25
38938Not responding0 / 25
39254Not responding0 / 25
50861Not responding0 / 25
51670Not responding0 / 24
51687Not responding0 / 24
51800Not responding0 / 23
53041Not responding0 / 25
53988Not responding0 / 25
54318Not responding0 / 24
58208Not responding0 / 24
59126Not responding0 / 25
63837Not responding0 / 24
65149Not responding0 / 24

Questions about 174.138.171.34

Is 174.138.171.34 a proxy?

Not at this moment, but it has been. 70 of the 103 ports we track on 174.138.171.34 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.171.34 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.171.34?

Since May 28, 2026. We have run 26,861 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.