South Korea: free HTTPS proxies 🇰🇷
South Korea HTTPS: latest snapshot has no proxies marked working. See check history and last-seen times; recheck before use.
showing 1–33 of 33 (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.
| 3128 | HTTPS | 🇰🇷Dobong-gu | Transparent | ✓ | 263 ms | 84% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Transparent | ✓ | 263 ms | 52% | not working last alive | |
| 3084 | HTTPS | 🇰🇷Haman-gun | Transparent | ✓ | 280 ms | 49% | not working last alive | |
| 3152 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 269 ms | 49% | not working last alive | |
| 3020 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 271 ms | 49% | not working last alive | |
| 3072 | HTTPS | 🇰🇷Haman-gun | Transparent | ✓ | 271 ms | 49% | not working last alive | |
| 3120 | HTTPS | 🇰🇷Haman-gun | Transparent | ✓ | 270 ms | 49% | not working last alive | |
| 3176 | HTTPS | 🇰🇷Goseong-gun | Transparent | ✓ | 269 ms | 49% | not working last alive | |
| 3016 | HTTPS | 🇰🇷Busan | Transparent | ✓ | 254 ms | 49% | not working last alive | |
| 3120 | HTTPS | 🇰🇷Changwon-si | Transparent | ✓ | 269 ms | 49% | not working last alive | |
| 3156 | HTTPS | 🇰🇷Nam-gu | Transparent | ✓ | 276 ms | 49% | not working last alive | |
| 3080 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 276 ms | 49% | not working last alive | |
| 3184 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 276 ms | 49% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 259 ms | 49% | 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 → | ||||||||
| 3064 | HTTPS | 🇰🇷Nam-gu | Transparent | ✓ | 278 ms | 49% | not working last alive | |
| 8080 | HTTPS | 🇰🇷Incheon | Elite | ✓ | 217 ms | 48% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Transparent | ✓ | 277 ms | 41% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 232 ms | 38% | not working last alive | |
| 8008 | HTTPS | 🇰🇷Chuncheon | Elite | ✓ | 258 ms | 34% | not working last alive | |
| 3032 | HTTPS | 🇰🇷Gimhae | Transparent | ✓ | 266 ms | 34% | not working last alive | |
| 12121 | HTTPS | 🇰🇷Yongin-si | Elite | ✓ | 1558 ms | 32% | not working last alive | |
| 8080 | HTTPS | 🇰🇷Gasan-dong | Anonymous | ✓ | 5944 ms | 30% | not working last alive | |
| 20000 | HTTPS | 🇰🇷Anyang-si | Elite | ✓ | 3318 ms | 26% | not working last alive | |
| 3180 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 269 ms | 19% | not working last alive | |
| 9443 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 233 ms | 17% | not working last alive | |
| 3116 | HTTPS | 🇰🇷Changwon | Transparent | ✓ | 348 ms | 15% | not working last alive | |
| 38157 | HTTPS | 🇰🇷Pyeongtaek-si | Elite | ✓ | 290 ms | 13% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Transparent | ✓ | 7278 ms | 10% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 8688 ms | 8% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Transparent | ✓ | 1619 ms | 8% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Transparent | ✓ | 241 ms | 6% | not working last alive | |
| 3128 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 4985 ms | 4% | not working last alive | |
| 8090 | HTTPS | 🇰🇷Seoul | Elite | ✓ | 233 ms | 2% | 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.
This slice groups public proxy records for South Korea / 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
- anonymous proxies HTTPS
- free proxy list
- HTTPS ip address
- HTTPS proxies online
- http proxies list txt
- dedicated ip for business
- how to check working proxies
- what is a SOCKS5 proxy
- free proxies by country
- working elite proxies
- SOCKS5 & HTTP proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.