How we check public VPN servers

checker methodology summary

PublicVPNList imports public OpenVPN profile candidates, parses endpoint metadata, runs automated checks, and publishes only rows with useful public country data, config availability and live measurement signals. The checker methodology summary is designed to explain the visible catalog, not to endorse the operator behind any endpoint.

What the checks measure

• reachability checks confirm that a candidate endpoint can answer the current checker workflow.
• latency measurement shows round-trip time in milliseconds from the checker location.
• speed/throughput caveats apply because Mbps is a short-term measurement from one route, not a permanent capacity promise.
• freshness windows separate fresh, recent, old and stale rows so older checks do not look current.
• confidence explanation combines live metrics and available recent check history where the dataset has enough evidence.
• Checked shows the latest successful date available for the endpoint in the dataset.

How to read the data

Public VPN endpoints can change quickly. A server with a fresh check, realistic speed and low latency is usually a better choice than an old endpoint with a large historic speed number. For sensitive activity, use a trusted provider instead of an unknown public server.

why score is not privacy score: the technical score compares usability signals such as freshness, speed, latency, stability and config availability. It does not verify operator identity, logging policy, jurisdiction or traffic handling.

For transparency, the catalog shows fresh measurements directly in the table, while direct raw .ovpn file access is blocked and downloads use short-lived links.

Source import and measurement are separate

The importer can collect public OpenVPN profiles before they have a current performance result. A profile from a source is only a candidate; the visible catalog is based on checked rows with useful metrics, country data and a downloadable profile path.

When a metric shows a dash, it means the value is unknown or not measured yet. It does not mean the server literally measured at zero. Empty country pages are marked noindex until live measured servers appear.

Limits of public VPN checks

• Tests run from our monitoring environment, so your route can be faster or slower depending on your network and location.
• Some servers block short probes but still work in a full OpenVPN client, while other servers can go offline after a successful check.
• Public VPN profiles are operated by third parties. Review the configuration and avoid sensitive activity unless you trust the operator.
• Sources can publish stale or duplicate profiles, so the catalog keeps filtering, sorting and refreshing instead of treating imports as final.

Data sources and removals

The source list is documented on the VPN data sources page. If a profile should be removed, send the server host, source URL and removal reason through the contact page so the entry can be reviewed.

source limitations: source labels describe discovery, not ownership. stale/dead policy: endpoints with old, failed or missing checks are hidden from public tables and noindexed where appropriate. report dead server process: use the server page report link with the server ID and observed failure so the endpoint can be reviewed.