Open Port Checker

Find out whether a TCP port on a host accepts connections from the internet. Your own public address is filled in so you can test your router first.

Common Ports:

How this port check works

When you press Check Port Status, our server attempts a TCP connection to the host and port you entered and waits up to 5 seconds for an answer. A TCP connection starts with the three-way handshake described in RFC 9293: our server sends a SYN, the target replies with SYN-ACK if something is listening, and our server completes it with an ACK and then closes the connection without sending any data.

The host field starts with your own public IP address, as our server sees it, so you can test your own router's port forwarding with one click. Replace it with any hostname or address to check another server. Because the connection comes from our server and not from your computer, the result answers one specific question: can this port be reached from the public internet right now?

The test covers TCP only. UDP has no handshake, so there is no reliable way to tell from outside whether a UDP port is open; services such as WireGuard, OpenVPN in its default mode and most game voice traffic cannot be checked here. A check is a single connection attempt, so it also says nothing about speed or packet loss.

Reading the result

Port is open

What happened: the handshake completed, so a service accepted the connection. The time shown is how long our server waited for the SYN-ACK.

What it does not prove: that the service is configured correctly or that it will accept your login. It only shows that something is listening and reachable.

Port is closed

What happened: the host answered with a reset (connection refused). The machine is online and reachable, but nothing is listening on that port, or a firewall is set to reject rather than drop.

Connection timed out

What happened: no answer arrived within 5 seconds. The host may be offline, a firewall may be silently dropping packets, the port may not be forwarded, or the address may be wrong.

Also shown here: a hostname that does not resolve. In that case the error line underneath carries the resolver's message, such as "Name or service not known", and the DNS Checker will show whether the name has an A record at all.

Testing your own port forwarding

Keep the prefilled address, enter the port you forwarded, and run the check. If the result is not "open", work through these in order; each one is a common cause.

Open ports, security, and other people's servers

An open port is exactly as risky as the service behind it. A current, patched web server on 443 is routine; a database, remote desktop or file-sharing service open to the internet is a frequent cause of break-ins, because those services were designed for trusted networks and are probed constantly by automated scanners. Expose only what has to be public, keep it updated, and put administrative services behind a VPN or SSH tunnel instead of forwarding them. Treat UPnP, which lets applications open ports on the router by themselves, and the router's DMZ option, which forwards every port to one device, as features to switch off unless you need them.

Check only hosts you run or have permission to test. A single connection attempt looks like any ordinary client and does no harm, but repeatedly probing ports on servers you do not control can breach the acceptable-use terms of their operator or your own provider. If you only need to know whether a web or mail host is up, the Ping Tool makes the same single TCP connection and also shows the address the name resolved to.

Common ports

The port a service uses is whatever it is configured to use; these are the registered defaults. The complete list is the IANA Service Name and Port Number Registry.

Port Service Notes
21FTPSends passwords in plain text; SFTP over port 22 is the usual replacement.
22SSH / SFTPEncrypted; a constant target for password guessing, so use key authentication.
25SMTPServer-to-server mail. Many ISPs block it outbound; clients submit on 587.
53DNSMostly UDP, which this tool cannot test; TCP 53 is used for large answers and zone transfers.
80HTTPUnencrypted web. Most sites keep it open only to redirect to 443.
443HTTPSEncrypted web traffic.
3306MySQL / MariaDBShould not be reachable from the internet; connect through SSH or a VPN.
3389RDPWindows remote desktop. Reach it over a VPN rather than forwarding it.
5432PostgreSQLSame advice as MySQL; restrict clients in pg_hba.conf as well.
8080HTTP alternateDevelopment servers, proxies and application containers.
25565Minecraft (Java)Open it only while hosting, and use the server's whitelist.

Frequently asked questions

Can this tool check UDP ports?

No. A UDP service does not acknowledge connections, so an outside probe cannot tell "open" from "dropped by a firewall" without sending protocol-specific traffic. Test UDP services with the application itself, for example by connecting a VPN client from a mobile connection.

The port is open but the application still does not work. Why?

"Open" means the operating system accepted a TCP connection. The application may still reject the client for its own reasons: wrong credentials, a hostname mismatch in a certificate, an application-level allowlist, or a different protocol version. Check the application's own log on the server.

Why does a check from inside my network give a different answer?

From inside, you connect to your router's public address and rely on it to loop the connection back in, which many routers do not do (the feature is called NAT loopback or hairpinning). From a phone on mobile data or from this tool, the connection arrives from outside, which is what remote users experience.

How do I see which ports are open on my own computer?

On Windows, open Command Prompt and run netstat -an | findstr LISTENING. On macOS or Linux, run ss -tlnp or netstat -tlnp. Those list the ports your machine is listening on locally; this tool tells you which of them the internet can actually reach.