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.
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.
- The service is not listening on all interfaces. On the device itself, run
netstat -an (Windows) or ss -tlnp (Linux, macOS) and confirm the port is bound to 0.0.0.0 or your LAN address, not only to 127.0.0.1.
- The device firewall blocks it. Windows Defender Firewall, the macOS firewall and Linux nftables or iptables all drop inbound connections unless a rule allows the port, regardless of what the router does.
- The router rule points at the wrong LAN address. Devices on DHCP can change address after a reboot. Give the device a fixed address or a DHCP reservation and check that the rule matches.
- You have two routers. An ISP modem-router in front of your own router means two layers of NAT; forward the port on both, or put the first one in bridge mode.
- Your provider uses carrier-grade NAT. If the WAN address on your router is in 100.64.0.0/10, the range reserved by RFC 6598, or simply does not match the public address shown on What Is My IP, inbound connections cannot reach you. Only the provider can change that, usually by selling a public address.
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 |
| 21 | FTP | Sends passwords in plain text; SFTP over port 22 is the usual replacement. |
| 22 | SSH / SFTP | Encrypted; a constant target for password guessing, so use key authentication. |
| 25 | SMTP | Server-to-server mail. Many ISPs block it outbound; clients submit on 587. |
| 53 | DNS | Mostly UDP, which this tool cannot test; TCP 53 is used for large answers and zone transfers. |
| 80 | HTTP | Unencrypted web. Most sites keep it open only to redirect to 443. |
| 443 | HTTPS | Encrypted web traffic. |
| 3306 | MySQL / MariaDB | Should not be reachable from the internet; connect through SSH or a VPN. |
| 3389 | RDP | Windows remote desktop. Reach it over a VPN rather than forwarding it. |
| 5432 | PostgreSQL | Same advice as MySQL; restrict clients in pg_hba.conf as well. |
| 8080 | HTTP alternate | Development servers, proxies and application containers. |
| 25565 | Minecraft (Java) | Open it only while hosting, and use the server's whitelist. |