Public VPN risk matrix
| Risk | What it means | How to reduce it |
| Unknown operator | You may not know who controls the endpoint | Use for low-risk testing only |
| Logging | Operator may log metadata or traffic patterns | Avoid sensitive accounts |
| DNS leaks | DNS may not follow the tunnel | Run DNS leak test |
| Stale endpoints | Public servers disappear or change | Use fresh checked rows |
| Jurisdiction unknown | Legal/privacy environment is unclear | Do not rely on it for privacy guarantees |
| Malicious or unsafe profiles | Profile may contain unexpected directives | Review .ovpn before connecting |
What PublicVPNList checks
PublicVPNList checks reachability, speed, latency, config availability and the last successful check time for public OpenVPN endpoints.
What PublicVPNList does not check
PublicVPNList does not verify VPN operator identity, logging policy, jurisdiction, long-term privacy, content filtering or traffic handling.
Safe use cases
Use public endpoints for OpenVPN setup practice, route tests, protocol comparison, low-risk browsing checks and troubleshooting.
Unsafe use cases
Avoid banking, private work accounts, sensitive identity sessions, admin panels and anything requiring a trusted VPN operator.