HProxy · Free South Korea pool
Free South Korea proxy list 2026
Each Korean entry below keeps its place only while our checker still hears from it within two days. More than two in three sit on eight Amazon addresses that carried nothing in our test.
South KoreaEliteSouth KoreaAnonymousSouth KoreaTransparentYou're viewing free South Korean proxies. See the full list.
Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
South Korea proxies right now, by the numbers
The pool currently holds 285 South Korea proxies spread across 11 different networks. They respond in 2614ms at the median, close to the 2394ms median across the whole free pool. The busiest exits are Incheon, Gwacheon-si, Seoul. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
What we saw when we tested the Korean list
These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.
Verify before you use
Run any list through the Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free South Korean proxies.
Here you get the free South Korean proxies our checker could still reach during the past two days. Type an entry's address and port into the proxy settings of your browser or tool. Sites then usually see a Korean address; in our test, four of 22 working entries exited abroad.
At 19:58 UTC on 27 September 2026, the list carried 329 entries, and just 32 were live. Across our whole pool, 17,348 entries were live in that same minute. Off busy addresses, our engine retired 6,568 Korean entries since May, and 5,680 never answered once.
Our test at 01:17 UTC on 28 September found 187 of the 269 rows on eight Amazon addresses. All were placed in Incheon and offered as HTTPS, and none carried a request anywhere. When we asked them for Cloudflare, 46 handed back a certificate our server could not verify.
The remaining 82 entries were spread over 58 addresses in 10 networks. Twenty-two relayed our echo in our test, 13 of them from the listed Korean address. Four more left from other addresses on Korea Telecom's network, and one from a Cloudflare address.
Most live Korean entries are not on datacenter space: 18 of the 32 at 19:58 UTC. Korea Telecom alone held 13 of those. Nobody can tell from a list whether the owner of such a line meant to share it.
Live Korean entries took a median 6.4 seconds to answer our server in the United States. The median Korean entry that worked and then died had lasted about 8 days; elsewhere, about 10. That comparison leaves out busy addresses, Amazon's networks and one June evening, on both sides. Work that needs a steady Korean address belongs on paid South Korean proxies.
01
South Korea against the rest of the free pool
Both columns below leave out busy addresses; the Korean one was read at 19:58 UTC.
| Measured 27 to 28 September 2026 | South Korea | Rest of the pool |
|---|---|---|
| Live entries measured | 32 | 3,983 |
| Median success rate across its own checks | 49.9% | 34.3% |
| Passed ten checks at 90 percent | 12.5% | 8.9% |
| Median latency from our server in the United States | 6,435 ms | 6,465 ms |
| Answered in under one second | 3.1% | 6.9% |
| Median lifespan of entries that died | 192 hours | 236 hours |
| Died within a day | 34.9% | 24.4% |
| Retired entries that never answered once | 86.5% | 88.7% |
| On datacenter address space | 43.8% | 23.0% |
The Korean live slice is our 19:58 UTC reading of 27 September. Retired shares and the rest column come from 12:16 UTC the next day, lifespans from 17:18. Every row drops addresses that hold 20 or more of the entries it counts. The lifespans skip Amazon's networks and one June evening on which our checker recorded mass deaths by mistake.
With 32 entries in the sample, one server can swing any share in this table. Korean entries tend to die early or last long: more than a third passed 30 days.
With its 34 busy addresses counted, Korea's retired share drops to 70.4 percent.
02
Eight Amazon addresses behind 187 of 269 entries
We pulled 269 Korean entries from our list API at 01:17 UTC on 28 September. Each was tested through itself: an echo service, then Cloudflare and Google, 30 seconds a request.
| Tested at 01:17 UTC, 28 September 2026 | On 8 Amazon addresses | On 58 other addresses |
|---|---|---|
| Entries on the list | 187 | 82 |
| Passed their latest check | 0 | 32 |
| Did not accept a connection | 100 | 32 |
| Completed at least one request | 0 | 25 |
| Relayed our echo with a visible exit | 0 | 22 |
| Exited in South Korea from the listed address | 0 | 13 |
| Opened Google | 0 | 9 |
| Failed a certificate check | 50 | 2 |
One HProxy server in the United States ran every request; ip-api.com named the exit countries. The Google row counts entries that fetched www.google.com/generate_204, its connectivity check.
Our checker keeps the Amazon rows because each passed some routine checks within the two days. A second pass at 01:21 UTC got 19 of them through the encrypted handshake, each carrying Cloudflare's name. Our server could verify none, and most issuers read like device names, such as HP-Procurve-Switch and FortiGate. One named a real GlobalSign authority, and at 05:23 UTC GlobalSign's own key refused its signature.
25 replied to a plain page request under 23 server names, and every reply read: Could not connect. We do not know who operates the eight servers; their replies fit a honeypot better than a proxy. In NIST's glossary, a honeypot is a system set up to attract intruders.
03
Where a free Korean proxy really exits
Just 13 of the 22 working entries used the listed address inside South Korea. Four Korea Telecom entries on ports 8090 and 8091 left from other Korea Telecom addresses.
Of the four that exited abroad, three left from the listed address, in Pakistan and England. Our list and the echo service place those three addresses in different countries. The fourth came out in Paris from another address. Asked through the working entries, Cloudflare answered nine from its Seoul data center and two from abroad.
By the Tor Project's own check, none of the entries it could reach sent our request into Tor.
04
Two Korean entries that read encrypted traffic
A live entry on an Alibaba address offered a Cloudflare certificate that was good for only two hours. It named a GlobalSign authority as its issuer, but GlobalSign's real certificate of that name rejected the signature.
The Seoul entry that exited in England failed our Cloudflare check as well. A proxy that merely relays would hand over the site's own certificate untouched. Treat such an entry as one that reads what you send.
05
How to use a free Korean proxy
Copy a row's address, port and protocol as one set, since the protocol decides how your tool connects. Read the Network column as well: no Amazon row carried traffic in our test.
Then load a page that reports your address and country, through the entry, before anything real. Four of the 22 Korean entries that relayed our echo came out in another country.
If the browser says your connection is not private, drop that entry and pick another. Nothing in a free SOCKS5 link is encrypted by the proxy itself. RFC 1928 leaves protection to the method both ends choose at the start. Open entries choose the method called no authentication required, which adds no protection.
Keep a few entries in reserve, because any one address can drop out between checks. Among Korean entries that died, more than one in three had lasted under a day.
Questions
Frequently asked.
Yes: nothing to pay and nothing to sign up for. The same entries are open to everyone, so test one just before a real task.
More than two in three of them are not working proxies. On 28 September 2026, 187 of 269 entries sat on 8 Amazon addresses, and none carried traffic.
From our server in the United States, the median live Korean entry answered in 6.4 seconds. The rest of our pool, busy addresses aside, needed about the same: 6.5 seconds.
Sometimes: 12 of the 32 Korean entries alive on 27 September 2026 were listed in Seoul. The Amazon entries listed in Incheon carried no traffic in our test.
The working ones mostly do. We tested them from our server in the United States on 28 September 2026. Of 22 relaying entries, 18 exited in Korea, 13 of them from the listed address. Four exited abroad.
Only for public browsing: the operator of an entry can read anything you send unencrypted. In our test, 52 Korean entries failed a certificate check, 50 of them on Amazon. Keep passwords and card numbers off every free entry.
Korean entries that answered and later died had a median lifespan of about 8 days. For the rest of our pool, it was 10. A third died within a day. Busy addresses, Amazon's networks and one June evening of checker failure are not counted.
For a job that cannot stop, HProxy sells South Korea proxies with targeting down to the city. There is no subscription to keep up, and purchased traffic has no scheduled expiry date.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
Docs and AI
The free list, in your assistant and in your code.
We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude, ChatGPT, Cursor or any assistant that speaks MCP, and the list's API is documented end to end.
Every product has its own reference in the docs. Something the list does not give you? Tell us.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
Let your assistant pull the list
The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.
The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.
All the machine lanes- MCP server
- Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from the free HProxy app's command line. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Comes with the free HProxy app: hproxy.com/proxy-checker - REST, no key
- Plain HTTP with CORS on, which is all an agent with a fetch tool needs.
curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"
Instructions for an assistant, in full
Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.
You can use HProxy's free proxy list, which needs no API key and no account.
GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.
Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it.
These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt
There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.