TCP 443 OpenVPN servers
TCP 443 OpenVPN profiles are useful on networks where HTTPS traffic is allowed but other VPN ports are blocked. This list focuses on live public OpenVPN servers using TCP port 443.
TCP 443 OpenVPN profiles are useful on networks where HTTPS traffic is allowed but other VPN ports are blocked. This list focuses on live public OpenVPN servers using TCP port 443.
Port 443 is commonly used for HTTPS, so TCP OpenVPN profiles on this port are often easier to test behind restrictive firewalls. Results are sorted by measured speed, then latency.
Filter condition: only public OpenVPN rows that match this page intent and have useful live metrics. Exclusion rules: stale, dead, duplicate, private/reserved, missing-country and no-metric rows are removed before sitemap inclusion.
Safety note
TCP 443 can be useful on restrictive networks, but it is not a privacy guarantee and it is not invisible. Treat it as a connectivity option, not as proof that the VPN operator is trustworthy. Compare freshness, latency and score before downloading, then verify IP and DNS after connecting.
This page is a focused view of the same live public VPN dataset used on the main catalog. Every row is selected from checked OpenVPN profiles and includes the country, host or IP address, protocol, port, measured download speed, latency and the last time the server was tested.
Speed shows the latest measured throughput and should be treated as a short-term quality signal, not a permanent guarantee. Latency shows how quickly the server answered from the test location. Public VPN endpoints can still disappear or change configuration without notice.
Use the table for quick discovery, then validate the downloaded .ovpn file before connecting. For privacy-sensitive browsing, also check your visible IP address and DNS leak behavior after the VPN connection is active.
Do not use these public endpoints for banking, private work accounts, sensitive identity sessions or any situation where you need a verified VPN operator. This list is for technical testing, setup practice, protocol comparison and low-risk routing checks.
| # | Country | Host / IP | Speed, Mbps | Network score | Freshness | Actions |
|---|---|---|---|---|---|---|
| 1 | Hong Kong | 45.125.0.246 45.125.0.246 |
908.1FastLow latencyTCP 443Stable | 80 | ||
| 2 | Japan | 219.100.37.193 219.100.37.193 |
694.6FastLow latencyTCP 443Stable | 96 | ||
| 3 | Japan | 219.100.37.117 219.100.37.117 |
558.9FastLow latencyTCP 443Stable | 96 | ||
| 4 | Japan | 219.100.37.162 219.100.37.162 |
432.7FastLow latencyTCP 443Stable | 96 | ||
| 5 | Japan | 219.100.37.23 219.100.37.23 |
245.8FastLow latencyTCP 443Stable | 96 | ||
| 6 | Japan | 219.100.37.58 219.100.37.58 |
215.9FastLow latencyTCP 443Stable | 96 | ||
| 7 | Japan | 219.100.37.110 219.100.37.110 |
197.7FastLow latencyTCP 443Stable | 96 | ||
| 8 | Japan | 219.100.37.106 219.100.37.106 |
185.6FastLow latencyTCP 443Stable | 96 | ||
| 9 | Japan | 219.100.37.215 219.100.37.215 |
182.7FastLow latencyTCP 443Stable | 96 | ||
| 10 | Japan | 219.100.37.221 219.100.37.221 |
153.1FastLow latencyTCP 443Stable | 96 | ||
| 11 | Japan | 219.100.37.81 219.100.37.81 |
142.4FastLow latencyTCP 443Stable | 80 | ||
| 12 | Japan | 219.100.37.177 219.100.37.177 |
112.8FastLow latencyTCP 443Stable | 80 | ||
| 13 | Japan | 219.100.37.180 219.100.37.180 |
105.6FastLow latencyTCP 443Stable | 80 | ||
| 14 | Japan | 219.100.37.98 219.100.37.98 |
95.1Usable speedLow latencyTCP 443Stable | 79 | ||
| 15 | Japan | 219.100.37.116 219.100.37.116 |
90.6Usable speedLow latencyTCP 443Stable | 94 | ||
| 16 | Japan | 219.100.37.178 219.100.37.178 |
89.2Usable speedLow latencyTCP 443Stable | 78 | ||
| 17 | Japan | 219.100.37.97 219.100.37.97 |
87.3Usable speedLow latencyTCP 443Stable | 77 | ||
| 18 | Japan | 219.100.37.19 219.100.37.19 |
83.7Usable speedLow latencyTCP 443Stable | 92 | ||
| 19 | Japan | 219.100.37.50 219.100.37.50 |
81.8Usable speedLow latencyTCP 443Stable | 76 | ||
| 20 | Japan | 219.100.37.179 219.100.37.179 |
75.7Usable speedLow latencyTCP 443Stable | 75 |