VPN protocol roadmap

This section is an informational status page. It does not publish imported metadata as a working VPN endpoint. The live catalog currently contains only OpenVPN profiles that pass the shared visibility, measurement and download checks.

Live checked OpenVPN catalog Checking methodology Source policy

What is imported today

The internal snapshot may contain OpenVPN, WireGuard and other protocol metadata for parser, deduplication and checker development. Imported means “stored for evaluation”; it does not mean reachable, authenticated, safe or ready to connect.

Internal metadata categories currently seen: openvpn, wireguard. Endpoint addresses and unverified connection details are intentionally not listed here.

What is actually published as live

Only OpenVPN rows with a valid host, protocol and port, a successful check within 24 hours, measured speed and latency, no current failure state, and an existing downloadable .ovpn profile can appear in live tables.

What is not published yet

WireGuard and credential-dependent protocols remain private metadata until protocol-specific external checkers can validate the complete connection material. Records marked metadata-only, unsupported, timed out, preflight-failed, TLS-insecure, missing credentials or using port 0 are excluded.

Admission criteria for another protocol

  1. Parse and validate the complete connection configuration without exposing credentials.
  2. Run a protocol-specific handshake and bounded traffic check from the external checker.
  3. Measure latency and throughput and record a recent successful check.
  4. Reject unsafe, duplicate, incomplete and credential-only records.
  5. Provide a safe connection or download flow and then pass the same visibility policy used by lists, pages and sitemap generation.