South Africa: free HTTPS proxies 🇿🇦
South Africa HTTPS: 4 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–32 of 32 (working first, then history)
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 443 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 1529 ms | 63% | ||
| 8080 | HTTPS | 🇿🇦South Jakarta | Anonymous | ✓ | 1829 ms | 21% | ||
| 8081 | HTTPS | 🇿🇦Brits | Transparent | ✓ | 3990 ms | 19% | ||
| 8080 | HTTPS | 🇿🇦Johannesburg | Transparent | ✓ | 4825 ms | 17% | ||
| 11080 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 170 ms | 49% | not working last alive | |
| 8865 | HTTPS | 🇿🇦Potchefstroom | Transparent | ✓ | 201 ms | 49% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Johannesburg | Transparent | ✓ | 176 ms | 49% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Durban | Transparent | ✓ | 184 ms | 48% | not working last alive | |
| 80 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 177 ms | 48% | not working last alive | |
| 9443 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 177 ms | 44% | not working last alive | |
| 443 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 173 ms | 44% | not working last alive | |
| 8005 | HTTPS | 🇿🇦Benoni | Transparent | ✓ | 173 ms | 38% | not working last alive | |
| 8102 | HTTPS | 🇿🇦Midrand | Transparent | ✓ | 6983 ms | 36% | not working last alive | |
| 8118 | HTTPS | 🇿🇦Centurion | Elite | ✓ | 8768 ms | 35% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 8005 | HTTPS | 🇿🇦Benoni | Transparent | ✓ | 3356 ms | 32% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Potchefstroom | Transparent | ✓ | 1071 ms | 25% | not working last alive | |
| 9999 | HTTPS | 🇿🇦Potchefstroom | Transparent | ✓ | 2570 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Cape Town | Elite | ✓ | 2743 ms | 20% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Johannesburg | Elite | ✓ | 6801 ms | 17% | not working last alive | |
| 8104 | HTTPS | 🇿🇦Kingsborough | Transparent | ✓ | 4994 ms | 16% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Brits | Transparent | ✓ | 4153 ms | 15% | not working last alive | |
| 9191 | HTTPS | 🇿🇦Jatiroto | Transparent | ✓ | 4161 ms | 15% | not working last alive | |
| 8102 | HTTPS | 🇿🇦Brits | Transparent | ✓ | 2276 ms | 14% | not working last alive | |
| 9999 | HTTPS | 🇿🇦Port Elizabeth | Transparent | ✓ | 6212 ms | 14% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Jakarta | Transparent | ✓ | 5368 ms | 12% | not working last alive | |
| 8088 | HTTPS | 🇿🇦Lamberts Bay | Transparent | ✓ | 8933 ms | 12% | not working last alive | |
| 8090 | HTTPS | 🇿🇦Johannesburg | Transparent | ✓ | 1555 ms | 12% | not working last alive | |
| 3128 | HTTPS | 🇿🇦Cape Town | Elite | ✓ | 2967 ms | 11% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Johannesburg | Transparent | ✓ | 2101 ms | 10% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Jakarta | Transparent | ✓ | 5094 ms | 9% | not working last alive | |
| 8080 | HTTPS | 🇿🇦Cape Town | Transparent | ✓ | 169 ms | 9% | not working last alive | |
| 9999 | HTTPS | 🇿🇦Port Elizabeth | Transparent | ✓ | 4411 ms | 5% | not working last alive | |
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
At a glance
This page has 4 entries marked working. Mean recorded check success across these entries is 30%; mean recorded response time, where available, is 3043 ms. By protocol: HTTPS (4). By anonymity level: Elite (1), Anonymous (1), Transparent (2). The most common ports are 8080, 443, 8081. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for South Africa / HTTPS. Use the recorded status and timestamps to interpret the table, then recheck before use. Availability and anonymity labels do not certify operator trust or privacy.
For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.
Free proxies — FAQ
How often is this free proxy list checked?
Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.
Are free public proxies safe to use?
Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.
How do I use a proxy from this list?
Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
People found this page by searching for
- HTTPS
- HTTPS proxy list
- proxy server HTTPS
- free proxy list
- free HTTPS proxy
- http proxies
- what is a SOCKS5 proxy
- proxy list
- public proxies for scraping
- socks5 proxies by country
- socks5 proxies
- dedicated ip step by step
- public proxies
- anonymous proxies for windows
- SOCKS5 & HTTP proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.