HProxy · Proxy database
Proxy detectedIPv4

Is 174.138.162.237 a proxy?

Yes. 174.138.162.237 is listed in the HProxy free proxy database as a public proxy, exiting from Phoenix, Arizona, United States. It was last seen alive 4 minutes ago.

Status
Recently alive
Last alive 4 minutes ago
Protocols
Unknown
75 open ports
Anonymity
Unknown
Not graded
Location
United States
Phoenix, Arizona, United States
Network / ISP
SECURED SERVERS LLC
AS20454 · datacenter
Performance
Unknown
30% uptime · 13 sources
Open proxy ports on 174.138.162.237
8001
-
-
-
Last alive 5 hours ago
8009
-
-
-
Last alive 5 hours ago
8080
-
-
-
Last alive 12 hours ago
8254
-
-
-
Last alive 49 minutes ago
8693
-
-
-
Last alive 7 hours ago
8880
-
-
-
Last alive 2 hours ago
9050
-
-
-
Last alive 2 hours ago
9051
-
-
-
Last alive 1 hour ago
9058
-
-
-
Last alive 2 hours ago
9059
-
-
-
Last alive 1 hour ago
9062
-
-
-
Last alive 7 hours ago
9190
-
-
-
Last alive 3 hours ago
9991
-
-
-
Last alive 12 hours ago
20074
-
-
-
Last alive 43 minutes ago
20320
-
-
-
Last alive 2 hours ago
21336
-
-
-
Last alive 2 hours ago
30280
-
-
-
Last alive 2 hours ago
30715
-
-
-
Last alive 4 minutes ago
30816
-
-
-
Last alive 7 hours ago
30849
-
-
-
Last alive 59 minutes ago
31044
-
-
-
Last alive 12 hours ago
31291
-
-
-
Last alive 8 hours ago
31540
-
-
-
Last alive 6 hours ago
32324
-
-
-
Last alive 3 hours ago
32380
-
-
-
Last alive 7 hours ago
32476
-
-
-
Last alive 1 hour ago
32522
-
-
-
Last alive 7 hours ago
33246
-
-
-
Last alive 2 hours ago
34117
-
-
-
Last alive 7 hours ago
35216
-
-
-
Last alive 4 hours ago
35672
-
-
-
Last alive 3 hours ago
35720
-
-
-
Last alive 3 hours ago
36452
-
-
-
Last alive 29 minutes ago
37073
-
-
-
Last alive 9 hours ago
37079
-
-
-
Last alive 3 hours ago
37229
-
-
-
Last alive 7 hours ago
37484
-
-
-
Last alive 6 hours ago
37539
-
-
-
Last alive 3 hours ago
37873
-
-
-
Last alive 2 hours ago
37896
-
-
-
Last alive 3 hours ago
38111
-
-
-
Last alive 1 hour ago
38965
-
-
-
Last alive 7 hours ago
39256
-
-
-
Last alive 7 hours ago
50307
-
-
-
Last alive 2 hours ago
50465
-
-
-
Last alive 7 hours ago
50790
-
-
-
Last alive 2 hours ago
51288
-
-
-
Last alive 4 hours ago
51382
-
-
-
Last alive 22 minutes ago
51481
-
-
-
Last alive 2 hours ago
51595
-
-
-
Last alive 7 hours ago
51763
-
-
-
Last alive 15 minutes ago
51773
-
-
-
Last alive 2 hours ago
52059
-
-
-
Last alive 2 hours ago
52919
-
-
-
Last alive 3 hours ago
53081
-
-
-
Last alive 2 hours ago
53201
-
-
-
Last alive 7 hours ago
53504
-
-
-
Last alive 1 hour ago
53621
-
-
-
Last alive 2 hours ago
54001
-
-
-
Last alive 3 hours ago
54376
-
-
-
Last alive 15 minutes ago
55100
-
-
-
Last alive 4 hours ago
55338
-
-
-
Last alive 7 hours ago
55523
-
-
-
Last alive 7 hours ago
55732
-
-
-
Last alive 4 hours ago
55945
-
-
-
Last alive 7 hours ago
56316
-
-
-
Last alive 2 hours ago
56621
-
-
-
Last alive 4 hours ago
57145
-
-
-
Last alive 10 hours ago
57369
-
-
-
Last alive 3 hours ago
58023
-
-
-
Last alive 6 hours ago
58104
-
-
-
Last alive 15 hours ago
62342
-
-
-
Last alive 7 minutes ago
63665
-
-
-
Last alive 2 hours ago
63724
-
-
-
Last alive 13 hours ago
64983
-
-
-
Last alive 4 hours ago

What this report means

A proxy on an IP address means that address is running a server that forwards other people’s traffic. When you route a request through it, the site you visit sees the proxy’s IP instead of yours. Public proxies like the ones in this database are open for anyone to use, which is exactly why they are useful for quick tests and equally why they are unreliable: they are shared by large numbers of strangers and run on infrastructure nobody is paid to maintain.

People look up whether a specific IP is a proxy for two main reasons. The first is to use it: you found 174.138.162.237 on a list and want to know if it is alive, what protocols it speaks, and where it exits before pointing a scraper or browser at it. The second is to defend against it: you run a site and want to know if traffic from 174.138.162.237 is coming through an open proxy, so you can decide whether to challenge or block it. This page answers both from the same data.

Whichever side you are on, remember that free, public proxies are unstable by nature. An IP that is alive right now can be dead within minutes, anonymity grades are best-effort rather than guaranteed, and popular addresses are often already rate-limited or blocked by large sites. Never send passwords, payment details or anything sensitive through a public proxy, and always verify an IP right before you depend on it. For work that has to keep running, dedicated or cleanly rotated paid proxies are the dependable alternative.

Frequently asked

Is 174.138.162.237 a proxy?

Yes. 174.138.162.237 appears in the HProxy free proxy database as a public proxy, with 75 open proxy ports (unknown protocol). Free proxies come and go, so its live status is rechecked continuously and may change.

What protocols does 174.138.162.237 support?

174.138.162.237 was seen speaking an unknown protocol on ports 8001, 8009, 8080, 8254, 8693, 8880, 9050, 9051, 9058, 9059, 9062, 9190, 9991, 20074, 20320, 21336, 30280, 30715, 30816, 30849, 31044, 31291, 31540, 32324, 32380, 32476, 32522, 33246, 34117, 35216, 35672, 35720, 36452, 37073, 37079, 37229, 37484, 37539, 37873, 37896, 38111, 38965, 39256, 50307, 50465, 50790, 51288, 51382, 51481, 51595, 51763, 51773, 52059, 52919, 53081, 53201, 53504, 53621, 54001, 54376, 55100, 55338, 55523, 55732, 55945, 56316, 56621, 57145, 57369, 58023, 58104, 62342, 63665, 63724, 64983. HTTP and HTTPS proxies carry web traffic; SOCKS4 and SOCKS5 carry any TCP traffic.

Is the proxy on 174.138.162.237 safe to use?

Treat it with caution. It is a public proxy that anyone can route through, so never send passwords, payment details or other sensitive data through it. Free proxies are fine for low-stakes testing, but for anything serious use a trusted paid provider.

Why might 174.138.162.237 stop working?

Free proxies are shared by many users and run on infrastructure no one is paid to maintain, so they get overloaded, rate-limited or shut down constantly. An IP that is alive now can be dead within minutes. Always verify right before you rely on it.

How do I block proxy traffic from 174.138.162.237?

If you run a site and want to block this proxy, deny the IP at your firewall, WAF or application layer. Because free proxy IPs change constantly, blocking individual addresses is a moving target, so most teams use a continuously updated proxy and abuse database rather than a static blocklist.

Need proxies that don’t die?

HProxy residential, ISP, mobile and datacenter proxies. Real uptime and speed, clean IPs that are not pre-blocked, pay by the gigabyte, no subscription.

See plans
Is 174.138.162.237 a proxy? Free proxy check and report | HProxy