OpenVPN config validator

Paste or upload a public .ovpn profile before importing it into OpenVPN. The validator reads the config locally in your browser and extracts the remote host, protocol, port, DNS directives, certificate blocks and options that deserve review.

Check an OpenVPN .ovpn file before connecting

Public OpenVPN configs are convenient, but they can hide details that matter: the server you connect to, whether the profile uses TCP or UDP, which port is used, whether all traffic is redirected through the VPN, and whether DNS settings are pushed by the server. This tool helps you inspect those details before you import the profile into OpenVPN Connect, OpenVPN GUI, Tunnelblick, NetworkManager or an Android OpenVPN app.

The validator is designed for quick safety review, not for proving that a VPN provider is trustworthy. A clean config can still connect to a third-party server that logs traffic or changes behavior later. Use the result together with the live server table, the DNS leak checklist and your own judgement before sending sensitive traffic through a public VPN endpoint.

Paste .ovpn config

Files are read locally in your browser. Maximum size: 256 KB.

Validation result

Paste a config and run validation.

What this validator checks

  • Remote host and port: shows the VPN endpoint from the remote line so you can compare it with the source page.
  • Protocol: detects tcp, tcp-client or udp usage and helps you choose the right network path.
  • DNS options: highlights pushed DNS directives such as dhcp-option DNS, which can affect leak behavior.
  • Certificate block: tells you whether an inline <ca> block is present or whether the profile expects local certificate files.
  • Risky directives: flags script hooks, credential-file references, compression and full-traffic redirect options for manual review.

Privacy and file limits

The upload field does not send your file to PublicVPNList. The browser reads the file locally, checks that it looks like a text OpenVPN config, rejects oversized files above 256 KB, and refuses obvious non-config files such as HTML, PHP or binary data. You can also paste the config manually if you do not want to select a file.

How to read the validation result

Start with the remote entries. They show where the OpenVPN client will connect and which port the profile expects. Then compare the detected protocol with your network situation: TCP can be easier on restricted networks, while UDP can feel faster when it is not blocked.

Warnings do not always mean the config is malicious. They mean the option deserves manual review before connecting. Script hooks, credential-file paths, compression and full-traffic redirect settings can all be legitimate in managed environments, but they are worth checking carefully in public VPN profiles from unknown sources.

Related OpenVPN tools

Frequently asked questions

Is the uploaded .ovpn file sent to the server?
No. The file is read locally in your browser and is not uploaded to PublicVPNList.
What does the validator check?
It extracts remote host, port, protocol, DNS options, certificate blocks and common risky directives such as script hooks or redirect-gateway.
Does a clean result mean the VPN is safe?
No. It only checks the config text. Public VPN servers are operated by third parties, so review the operator and avoid sensitive traffic on unknown endpoints.