Proxy.
Get Started

Is 174.138.162.203 a proxy? Yes, it was.

174.138.162.203 has been a working public proxy: 73 of the 99 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
99

ports recorded on this address

Answering now0
Ever answered73
Checks run14,352
First recorded2026-05-13
CountryUS United States
NetworkSECURED SERVERS LLC

Ports recorded on 174.138.162.203

We hold 99 ports on 174.138.162.203 and have run 14,352 checks against them. 73 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.203, with how many checks each has answered
PortStatusTimes answered
8001Not responding13 / 247
54493Not responding12 / 247
54597Not responding12 / 252
21620Not responding10 / 246
8019Not responding9 / 246
9494Not responding8 / 251
30559Not responding8 / 241
9991Not responding5 / 246
33958Not responding5 / 244
36206Not responding5 / 238
21551Not responding4 / 238
55710Not responding4 / 247
8181Not responding3 / 244
8086Not responding2 / 33
Show the other 85 ports on this page
The remaining ports HProxy has recorded on 174.138.162.203
PortStatusTimes answered
8220Not responding2 / 33
8254Not responding2 / 33
8706Not responding2 / 238
21534Not responding2 / 237
31972Not responding2 / 241
33381Not responding2 / 244
33761Not responding2 / 33
37060Not responding2 / 235
37564Not responding2 / 240
37802Not responding2 / 243
38015Not responding2 / 241
50869Not responding2 / 245
51763Not responding2 / 242
53198Not responding2 / 244
53636Not responding2 / 245
55346Not responding2 / 241
65310Not responding2 / 244
8022Not responding1 / 32
8080Not responding1 / 33
8081Not responding1 / 34
8109Not responding1 / 33
8865Not responding1 / 248
30278Not responding1 / 241
30941Not responding1 / 32
30947Not responding1 / 32
31000Not responding1 / 32
31002Not responding1 / 32
31939Not responding1 / 31
32099Not responding1 / 32
32241Not responding1 / 31
32650Not responding1 / 31
32897Not responding1 / 32
33212Not responding1 / 32
33525Not responding1 / 232
33870Not responding1 / 32
36003Not responding1 / 237
36155Not responding1 / 32
36213Not responding1 / 31
36536Not responding1 / 32
36845Not responding1 / 241
37234Not responding1 / 33
37403Not responding1 / 243
37734Not responding1 / 231
38683Not responding1 / 236
38843Not responding1 / 240
39142Not responding1 / 233
50759Not responding1 / 235
51523Not responding1 / 237
51563Not responding1 / 32
51992Not responding1 / 241
52400Not responding1 / 32
52626Not responding1 / 231
55443Not responding1 / 32
55608Not responding1 / 32
55991Not responding1 / 236
56465Not responding1 / 244
56629Not responding1 / 239
56748Not responding1 / 32
65223Not responding1 / 236
8090Not responding0 / 29
9050Not responding0 / 29
20204Not responding0 / 29
21064Not responding0 / 29
30898Not responding0 / 29
31182Not responding0 / 232
31438Not responding0 / 29
31454Not responding0 / 29
31705Not responding0 / 29
32166Not responding0 / 30
32439Not responding0 / 30
32764Not responding0 / 29
33332Not responding0 / 240
33661Not responding0 / 30
35106Not responding0 / 231
36429Not responding0 / 234
39066Not responding0 / 30
50001Not responding0 / 30
51621Not responding0 / 230
51632Not responding0 / 29
51985Not responding0 / 242
52168Not responding0 / 29
52267Not responding0 / 229
53164Not responding0 / 234
55053Not responding0 / 232
62929Not responding0 / 30

Questions about 174.138.162.203

Is 174.138.162.203 a proxy?

Not at this moment, but it has been. 73 of the 99 ports we track on 174.138.162.203 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.203 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.203?

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

Free proxies answering right now

View all →
FR

173.212.203.209:80

HTTP · France · 100% · 5ms

→DE

3.121.130.230:1088

HTTP · Germany · 15% · 10ms

→DE

18.185.103.130:443

HTTP · Germany · 99% · 13ms

→DE

63.181.83.210:9394

HTTP · Germany · 14% · 13ms

→DE

37.120.189.106:80

HTTP · Germany · 98% · 14ms

→DE

47.91.65.12:80

HTTP · Germany · 100% · 15ms

→

Where to go next

Free United States proxiesEvery live proxy exiting this country→More proxies on SECURED SERVERS LLCEverything we track on AS20454→The complete free proxy listEvery country, protocol and anonymity grade→

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.