HProxy · Proxy database
Proxy detectedIPv4

Is 63.179.134.206 a proxy?

Yes. 63.179.134.206 is listed in the HProxy free proxy database as a public proxy, exiting from Frankfurt am Main, Hesse, Germany. At least one port is responding right now.

Status
Alive now
Passing checks right now
Protocols
HTTP, HTTPS, SOCKS4, SOCKS5
41 open ports
Anonymity
Elite
No IP or proxy header leak
Location
Germany
Frankfurt am Main, Hesse, Germany
Network / ISP
Amazon.com, Inc.
AS16509 · datacenter
Performance
582 ms
67% uptime · 4 sources
Open proxy ports on 63.179.134.206
860
-
-
-
Last alive 44 minutes ago
1350
-
-
-
Last alive 1 hour ago
1372
-
-
-
Last alive 1 hour ago
1429
-
-
-
Last alive 2 hours ago
2048
-
-
-
Last alive 30 minutes ago
3667
https, socks4, socks5
elite
582 ms
Alive
3949
-
-
-
Last alive 1 hour ago
8561
-
-
-
Last alive 30 minutes ago
8658
-
-
-
Last alive 4 hours ago
10199
-
-
-
Last alive 4 hours ago
10755
-
-
-
Last alive 1 hour ago
13703
-
-
-
Last alive 32 minutes ago
14953
-
-
-
Last alive 4 hours ago
15892
-
-
-
Last alive 30 minutes ago
16901
-
-
-
Last alive 4 hours ago
21181
-
-
-
Last alive 30 minutes ago
21453
-
-
-
Last alive 30 minutes ago
22327
-
-
-
Last alive 3 hours ago
23529
-
-
-
Last alive 6 hours ago
25928
http, https, socks5
-
1004 ms
Alive
28369
-
-
-
Last alive 32 minutes ago
29512
-
-
-
Last alive 4 hours ago
32006
-
-
-
Last alive 52 minutes ago
32790
-
-
-
Last alive 1 hour ago
34763
-
-
-
Last alive 3 hours ago
37465
-
-
-
Last alive 30 minutes ago
40083
-
-
-
Last alive 28 minutes ago
40203
-
-
-
Last alive 22 minutes ago
43857
-
-
-
Last alive 30 minutes ago
43967
-
-
-
Last alive 30 minutes ago
46452
-
-
-
Last alive 28 minutes ago
48783
-
-
-
Last alive 4 hours ago
50164
-
-
-
Last alive 14 minutes ago
51417
-
-
-
Last alive 30 minutes ago
52742
-
-
-
Last alive 4 hours ago
52805
-
-
-
Last alive 31 minutes ago
54011
-
-
-
Last alive 4 hours ago
55288
-
-
-
Last alive 14 minutes ago
56531
-
-
-
Last alive 16 minutes ago
57018
-
-
-
Last alive 4 hours ago
57613
-
-
-
Last alive 28 minutes 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 63.179.134.206 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 63.179.134.206 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 63.179.134.206 a proxy?

Yes. 63.179.134.206 appears in the HProxy free proxy database as a public proxy, with 41 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 63.179.134.206 support?

63.179.134.206 was seen speaking http, https, socks4, socks5 on ports 860, 1350, 1372, 1429, 2048, 3667, 3949, 8561, 8658, 10199, 10755, 13703, 14953, 15892, 16901, 21181, 21453, 22327, 23529, 25928, 28369, 29512, 32006, 32790, 34763, 37465, 40083, 40203, 43857, 43967, 46452, 48783, 50164, 51417, 52742, 52805, 54011, 55288, 56531, 57018, 57613. HTTP and HTTPS proxies carry web traffic; SOCKS4 and SOCKS5 carry any TCP traffic.

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

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 63.179.134.206 a proxy? Free proxy check and report | HProxy