3.35.49.14:8080 HTTP proxy
This endpoint passed two HTTPS requests with valid destination certificates and a changed exit IP. Its source-reported location is South Korea. Measurements are from local-b and can differ on your network.
Endpoint facts and current evidence
- Proxy address
- 3.35.49.14:8080
- Connection protocol
- HTTP
- HTTPS capability
- Passed both HTTPS probes
- Endpoint location
- South Korea (source-reported)
- Last observed exit IP
- 3.35.49.14 (successful check)
- Latest attempt
- 2026-10-13 12:15:43 UTC
- Last successful check
- 2026-10-13 12:15:43 UTC
- First detailed observation
- 2026-10-13 11:06:06 UTC
- Assigned checker
- local-b
- Observed success
- 100% across 5 attempts
- Median successful response
- 2,114 ms across 5 retained successful checks
- Discovery sources
- proxyscrape
- Publication expiry
- 2026-10-13 13:15:43 UTC unless a later check changes status
- Authentication
- Imported without username or password
- UDP and sustained bandwidth
- Not measured
A pass confirms connectivity from one assigned checker to two test destinations. It does not verify operator identity, ownership, logging policy, anonymity or safety. Country is the endpoint’s reported location, not a guarantee about where a destination locates its exit IP.
Recent check history for 3.35.49.14:8080
This page retains up to 24 individual attempts received after detailed history was enabled. The lifetime attempt counters can therefore exceed the number of rows below. A failed check means the complete verification did not pass; it does not identify a specific cause. Missing measurements are never displayed as zero latency.
| Attempt time (UTC) | Result | HTTPS response | Observed exit IP |
|---|---|---|---|
| Passed | 1,311 ms | 3.35.49.14 | |
| Passed | 2,397 ms | 3.35.49.14 | |
| Passed | 2,114 ms | 3.35.49.14 | |
| Passed | 2,502 ms | 3.35.49.14 | |
| Passed | 1,103 ms | 3.35.49.14 |
How to interpret this endpoint’s results
The assigned checker recorded 5 successful attempts out of 5 total attempts, an observed success rate of 100%. This sample reflects the checker’s schedule, destinations and network; it is not an uptime guarantee. Response time includes connection setup and a small HTTPS response. Read how checks work before comparing these values with speed or ping measurements from another tool.
How to test this HTTP proxy
Download and use the cURL configuration
The Download config (.conf) button saves this endpoint’s proxy setting and short connection timeouts. Run it with cURL and the HTTPS destination you want to test:
curl --config "publicvpnlist-http-3.35.49.14-8080.conf" https://api.ipify.orgThe Download address (.txt) button saves one protocol://IP:port line for clients that accept a proxy address. Availability is checked against the latest published results when you download. Follow the download guide for file formats and freshness limits.
For an application that accepts a proxy URI, use http://3.35.49.14:8080. In a host-and-port dialog, enter 3.35.49.14 as the host and 8080 as the port. Select HTTP explicitly.
This curl example routes only the single request through the endpoint. Compare the response with your direct public IP and keep certificate verification enabled.
curl --proxy http://3.35.49.14:8080 --max-time 10 https://api.ipify.orgFor HTTPS destinations, the client uses CONNECT through this HTTP proxy. The proxy URI remains http://; an https:// proxy URI describes TLS to the proxy itself and is a different feature.
Use the Firefox setup guide for a browser-only test. If a connection fails, check the protocol, port and latest check time before trying another endpoint. Never disable HTTPS certificate validation or provide personal account credentials to an unknown public proxy.
Recently checked alternatives
Prefer a fresh result matching your application’s protocol. The links below use the same country where available, then the same protocol.
All checked HTTP proxies · Proxy list for South Korea · All proxy countries
Proxy or VPN: choose the right connection
This endpoint is an application proxy. Read what a proxy does, compare Proxy vs VPN and review public proxy safety limits. For VPN profiles, use the separate OpenVPN server catalog or VPN and tunnel directory.
Source attribution and endpoint questions
This endpoint was discovered in ProxyScrape. PublicVPNList’s measurements are produced separately from source claims. See the source policy and retained license notices.
Is 3.35.49.14:8080 currently working?
The endpoint has a recent successful verification in the current catalog. The latest attempt was 2026-10-13 12:15:43 UTC. Availability from your network and to other destinations can differ.
Does the South Korea label prove the exit country?
No. It is the source-reported location of the endpoint address. The last successful check observed exit IP 3.35.49.14. A destination service may locate that exit differently or apply its own restrictions.
Why is the proxy page still here after a failed check?
Saved links retain their last measurements and recent history. An endpoint without a fresh successful result is removed from the live list and sitemap, and its detail page is marked noindex until it passes again.
For connection problems, see proxy troubleshooting. If you operate this endpoint or want to report incorrect metadata, use Contacts and include only the public address, protocol and approximate check time.