HProxy · Proxy database
Proxy detectedIPv4

Is 13.126.183.60 a proxy?

Yes. 13.126.183.60 is listed in the HProxy free proxy database as a public proxy, exiting from Mumbai, Maharashtra, India. At least one port is responding right now.

Status
Alive now
Passing checks right now
Protocols
HTTP, HTTPS, SOCKS4, SOCKS5
91 open ports
Anonymity
Elite
No IP or proxy header leak
Location
India
Mumbai, Maharashtra, India
Network / ISP
Amazon.com, Inc.
AS16509 · datacenter
Performance
261 ms
45% uptime
Reliability over time
Onlineup for 1d 8hReviving
24 hours44%
7 days15%
All-time22%
Verified 502× · last checked 1 day ago
Uptime, last 24h
18 of 144 ten-minute checks today
44%online
Uptime timeline, last 24 hours UTC: 44% online across 18 of 144 ten-minute checks. Gaps are slots that were not checked.UpDown00:0006:0012:0018:00UTC
Gaps are slots we didn’t check. This timeline is new, so it fills in over the day as verification runs.
Open proxy ports on 13.126.183.60
1088
socks4, socks5
elite
3193 ms
Alive
1285
-
-
-
Last alive 1 day ago
1695
-
-
-
Last alive 1 day ago
1876
-
-
-
Last alive 1 day ago
2050
-
-
-
Last alive 1 day ago
3586
-
-
-
Last alive 1 day ago
4300
-
-
-
Last alive 1 day ago
5576
-
-
-
Last alive 1 day ago
6010
-
-
-
Last alive 1 day ago
6026
-
-
-
Last alive 1 day ago
6076
-
-
-
Last alive 1 day ago
6197
-
-
-
Last alive 1 day ago
6401
-
-
-
Last alive 1 day ago
6681
-
-
-
Last alive 1 day ago
7193
-
-
-
Last alive 1 day ago
7386
-
-
-
Last alive 1 day ago
7660
-
-
-
Last alive 1 day ago
7890
-
-
-
Last alive 1 day ago
8118
-
-
-
Last alive 1 day ago
8216
http, socks4
-
773 ms
Alive
8819
http
-
3905 ms
Alive
8899
-
-
-
Last alive 1 day ago
9050
-
-
-
Last alive 1 day ago
9218
http, https, socks4, socks5
-
261 ms
Alive
9382
-
-
-
Last alive 1 day ago
9756
-
-
-
Last alive 1 day ago
9999
-
-
-
Last alive 1 day ago
10101
-
-
-
Last alive 1 day ago
10160
http
-
3430 ms
Alive
10665
-
-
-
Last alive 1 day ago
11273
-
-
-
Last alive 1 day ago
11523
-
-
-
Last alive 1 day ago
11586
-
-
-
Last alive 1 day ago
12282
-
-
-
Last alive 1 day ago
12441
-
-
-
Last alive 1 day ago
13290
http, https, socks4, socks5
-
2143 ms
Alive
14199
-
-
-
Last alive 1 day ago
14331
-
-
-
Last alive 1 day ago
15877
-
-
-
Last alive 1 day ago
16091
-
-
-
Last alive 1 day ago
18080
-
-
-
Last alive 1 day ago
18127
-
-
-
Last alive 1 day ago
18856
http, socks4
-
757 ms
Alive
19081
-
-
-
Last alive 1 day ago
19719
-
-
-
Last alive 1 day ago
20014
-
-
-
Last alive 1 day ago
21020
-
-
-
Last alive 1 day ago
22109
-
-
-
Last alive 1 day ago
23873
-
-
-
Last alive 1 day ago
24555
-
-
-
Last alive 1 day ago
26735
http, https, socks4
-
498 ms
Alive
27178
http, https, socks4
-
461 ms
Alive
27902
-
-
-
Last alive 1 day ago
28101
http, https, socks4, socks5
-
408 ms
Alive
29285
-
-
-
Last alive 1 day ago
30392
-
-
-
Last alive 1 day ago
31023
http, https, socks4, socks5
-
1141 ms
Alive
32062
-
-
-
Last alive 1 day ago
32069
-
-
-
Last alive 1 day ago
32213
-
-
-
Last alive 1 day ago
34766
-
-
-
Last alive 1 day ago
35619
-
-
-
Last alive 1 day ago
35870
-
-
-
Last alive 1 day ago
36756
-
-
-
Last alive 1 day ago
37917
-
-
-
Last alive 1 day ago
38276
-
-
-
Last alive 1 day ago
38565
http, https, socks4, socks5
-
267 ms
Alive
39062
-
-
-
Last alive 1 day ago
39376
http
-
261 ms
Alive
39517
-
-
-
Last alive 1 day ago
40988
-
-
-
Last alive 1 day ago
41974
-
-
-
Last alive 1 day ago
43279
-
-
-
Last alive 1 day ago
44018
-
-
-
Last alive 1 day ago
45227
-
-
-
Last alive 1 day ago
47369
-
-
-
Last alive 1 day ago
47507
http, https, socks4, socks5
-
4080 ms
Alive
47556
-
-
-
Last alive 1 day ago
47712
-
-
-
Last alive 1 day ago
48013
-
-
-
Last alive 1 day ago
49279
-
-
-
Last alive 1 day ago
51664
-
-
-
Last alive 1 day ago
54159
-
-
-
Last alive 1 day ago
54937
-
-
-
Last alive 1 day ago
55330
-
-
-
Last alive 1 day ago
55910
-
-
-
Last alive 1 day ago
56147
http, https, socks4, socks5
-
328 ms
Alive
56251
-
-
-
Last alive 1 day ago
57214
-
-
-
Last alive 1 day ago
58305
-
-
-
Last alive 1 day ago
59232
-
-
-
Last alive 1 day 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 13.126.183.60 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 13.126.183.60 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 13.126.183.60 a proxy?

Yes. 13.126.183.60 appears in the HProxy free proxy database as a public proxy, with 91 open proxy ports (http, https, socks4, socks5). Free proxies come and go, so its live status is rechecked continuously and may change.

What protocols does 13.126.183.60 support?

13.126.183.60 was seen speaking http, https, socks4, socks5 on ports 1088, 1285, 1695, 1876, 2050, 3586, 4300, 5576, 6010, 6026, 6076, 6197, 6401, 6681, 7193, 7386, 7660, 7890, 8118, 8216, 8819, 8899, 9050, 9218, 9382, 9756, 9999, 10101, 10160, 10665, 11273, 11523, 11586, 12282, 12441, 13290, 14199, 14331, 15877, 16091, 18080, 18127, 18856, 19081, 19719, 20014, 21020, 22109, 23873, 24555, 26735, 27178, 27902, 28101, 29285, 30392, 31023, 32062, 32069, 32213, 34766, 35619, 35870, 36756, 37917, 38276, 38565, 39062, 39376, 39517, 40988, 41974, 43279, 44018, 45227, 47369, 47507, 47556, 47712, 48013, 49279, 51664, 54159, 54937, 55330, 55910, 56147, 56251, 57214, 58305, 59232. HTTP and HTTPS proxies carry web traffic; SOCKS4 and SOCKS5 carry any TCP traffic.

Is the proxy on 13.126.183.60 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 13.126.183.60 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 13.126.183.60?

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.

More proxies on this network · Amazon.com, Inc.
Related free proxy lists

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