Live checked and technically verified. This config passed a full-tunnel HTTPS check and changed the checker's public exit IP. Current throughput, tunnel RTT, last successful check and OpenVPN download action are shown below. This technical check does not verify the third-party operator or privacy policy.
How the network score is calculated
This score compares current usability signals:
- Freshness: how recently the endpoint passed a check
- Speed: latest measured throughput
- Latency: round-trip time from the checker location
- Stability: recent successful and failed checks
- Config availability: whether a downloadable profile exists
Not a privacy or operator-trust score. It does not verify the VPN operator, logging policy, jurisdiction or traffic handling.
Expected .ovpn profile fields
Before importing the downloaded profile, compare these visible endpoint fields with the remote, proto and port values inside the file.
| remote | 219.100.37.128 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 11, 2026 13:25 UTC |
| source | AutoOVPN |
Safety note
TCP 443 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.
Server evidence summary
This detail page is built from the current published snapshot. The latest successful check for this endpoint is Sep 11, 2026 13:25 UTC, and the endpoint was first seen no later than Aug 14, 2026.
PublicVPNList stores the parsed endpoint, protocol, port, source label and measurement results so users can compare this server before downloading. The source label describes where the public profile was discovered; it does not prove who operates the VPN endpoint or what logging policy it follows.
Hover, focus or tap a point for check details.
Hover, focus or tap a point for check details.
Check history details
Recent checks are shown below. Rows labelled “current snapshot” show the latest published state; the other rows are saved check results. A failure counter describes consecutive failures, not the total number of failed rows shown here. Repeated failures deactivate an endpoint; inactive endpoints remain on the site with their check status and are retried. A later successful check can return them to the working list.
| Status | Checked | Speed | Ping | TTT | Failures |
|---|---|---|---|---|---|
| OK | Sep 11, 2026 13:25 UTC | 1.0 Mbps | 486 ms | 4245 ms | 0 |
| Fail | Sep 11, 2026 13:23 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 10, 2026 14:23 UTC | 2.1 Mbps | 254 ms | 4009 ms | 0 |
| OK | Sep 10, 2026 14:22 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 9, 2026 15:22 UTC | Unknown Mbps | 246 ms | 6832 ms | 0 |
| Fail | Sep 9, 2026 15:19 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 9, 2026 12:39 UTC | 2.8 Mbps | 275 ms | 5961 ms | 0 |
| OK | Sep 8, 2026 15:24 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 8, 2026 15:09 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| OK | Sep 8, 2026 12:39 UTC | 1.6 Mbps | 401 ms | 3518 ms | 0 |
| OK | Sep 7, 2026 12:37 UTC | 2.7 Mbps | 279 ms | 5583 ms | 0 |
| Fail | Sep 6, 2026 12:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 5, 2026 15:09 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 5, 2026 12:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 4, 2026 12:33 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 3, 2026 12:32 UTC | 1.6 Mbps | 280 ms | 3914 ms | 0 |
| OK | Sep 2, 2026 15:09 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 2, 2026 14:53 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 2, 2026 12:13 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 1, 2026 12:11 UTC | 2.4 Mbps | 265 ms | 4379 ms | 0 |
Alternative live VPN servers
Use these alternatives if this endpoint is slow from your route, the protocol is blocked, or the latest live test fails before download. Same-country alternatives preserve the location target; global alternatives prioritize measured speed and recent checks.