Yes. 13.246.6.135 is listed in the HProxy free proxy database as a public proxy, exiting from Cape Town, Western Cape, South Africa. At least one port is responding right now.
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.246.6.135 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.246.6.135 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.
Yes. 13.246.6.135 appears in the HProxy free proxy database as a public proxy, with 113 open proxy ports (http, https, socks4, socks5). Free proxies come and go, so its live status is rechecked continuously and may change.
13.246.6.135 was seen speaking http, https, socks4, socks5 on ports 695, 1248, 1966, 3172, 3800, 4145, 4387, 4824, 4953, 5336, 5633, 5678, 6432, 6616, 8118, 8119, 8447, 8800, 8860, 8894, 8899, 8957, 9050, 9230, 9283, 9844, 9933, 10258, 10909, 11580, 11702, 11714, 12005, 12354, 14037, 14291, 14850, 15858, 16001, 16425, 18372, 19075, 19190, 20028, 20104, 20340, 20496, 21351, 21426, 21452, 21572, 23553, 23772, 24787, 25339, 26607, 27293, 28133, 29432, 29587, 29684, 30329, 30732, 31736, 32252, 32762, 32880, 33411, 36293, 36615, 36685, 37648, 37828, 38238, 39003, 39202, 39260, 40506, 41260, 41715, 42169, 42186, 43502, 43653, 43772, 44210, 45999, 46234, 46430, 46619, 47069, 47407, 48072, 48134, 48483, 49817, 50167, 50701, 50834, 51327, 52336, 53413, 53668, 55307, 57638, 57840, 57871, 57996, 58262, 59513, 59648, 59713, 59739. HTTP and HTTPS proxies carry web traffic; SOCKS4 and SOCKS5 carry any TCP traffic.
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.
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.
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.
HProxy residential, ISP, mobile and datacenter proxies. Real uptime and speed, clean IPs that are not pre-blocked, pay by the gigabyte, no subscription.