Port check for VPN hosts
Test whether a TCP host and port are reachable from our server. For UDP OpenVPN profiles, use this as a basic helper only because browsers and short server probes cannot fully validate UDP tunnels.
Check TCP port
Enter a host and port.
How to interpret port check results
An open result means the PublicVPNList server could establish a TCP connection to the host and port you entered. That is a useful signal for OpenVPN TCP profiles on ports such as 443, 80, 1194 and other custom ports. A closed or blocked result can mean the service is down, a firewall blocks our test location, the host only accepts selected networks, or the profile uses UDP instead of TCP.
This test does not log in to OpenVPN and does not prove that a VPN tunnel will authenticate successfully. It only checks basic TCP reachability from our server at the moment of the test.
Common VPN ports to test
- 443 TCP: often works on restrictive networks because it resembles normal HTTPS traffic.
- 1194 TCP: a common OpenVPN port when the server is configured for TCP.
- 80 TCP: sometimes used as a fallback where only web traffic is allowed.
- Custom ports: public VPN sources may rotate ports, so always compare the test with the
remoteline in the.ovpnfile.
Frequently asked questions
- What does the port check test?
- It tries to open a TCP connection from the PublicVPNList server to the host and port you enter.
- Can this test UDP OpenVPN ports?
- No. This tool checks TCP reachability. UDP OpenVPN profiles need a full VPN or UDP-specific test.
- Why can a port look closed here but work for me?
- Firewalls and routing can differ by location. This test shows reachability from our server, not from every user network.