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.221 |
|---|---|
| proto | tcp |
| port | 443 |
| country | Japan |
| last checked | Sep 9, 2026 22:54 UTC |
| source | VPNGate |
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 9, 2026 22:54 UTC, and the endpoint was first seen no later than Aug 27, 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 9, 2026 22:54 UTC | 1.3 Mbps | 251 ms | 3208 ms | 0 |
| OK | Sep 9, 2026 22:51 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 8, 2026 23:52 UTC | 2.6 Mbps | 543 ms | 3421 ms | 0 |
| OK | Sep 8, 2026 23:51 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 8, 2026 23:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 1 |
| Fail | Sep 7, 2026 23:48 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 6, 2026 23:47 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 5, 2026 23:45 UTC | 1.3 Mbps | 284 ms | 6168 ms | 0 |
| OK | Sep 5, 2026 23:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 4, 2026 23:43 UTC | 1.7 Mbps | 352 ms | 3934 ms | 0 |
| Fail | Sep 3, 2026 23:42 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 2, 2026 23:41 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Sep 2, 2026 23:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Sep 1, 2026 23:41 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Aug 31, 2026 23:40 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Aug 30, 2026 23:39 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 30, 2026 23:35 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Aug 29, 2026 23:38 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| Fail | Aug 28, 2026 23:36 UTC | Unknown Mbps | Unknown ms | Unknown ms | 0 |
| OK | Aug 27, 2026 23:34 UTC | 1.6 Mbps | 468 ms | 3339 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.