Check whether a port on your own connection is reachable from the internet.
Example
What this means
Checked on this visit
Capabilities and processing
Choose a TCP port, or one of the common ones (SSH, HTTP, HTTPS, Remote Desktop, Minecraft, Plex, Jellyfin), and press Check. Our server makes one TCP connection attempt from Eastern North America to the public IP address your browser connected from, limited to 1.5 seconds, and sends nothing over it. It can only test your own address.
The result is open (connected, with the time), closed (the address answered and refused) or no answer (inconclusive). Each outcome comes with what to check next: the app and the address it listens on, the router's port forward, the device firewall, carrier-grade NAT and VPNs. Checks on this visit are listed in the tab, newest first.
Example workflow
Someone hosting a Minecraft server checks port 25565 and gets no answer. They add a TCP forward on the router to the computer running the server and check again: now it is closed, so the router forwards but nothing listens. After allowing the server through the computer's firewall, the port is open.
Limits and interpretation
Behind a VPN, proxy or carrier-grade NAT, the address tested belongs to that gateway, not your router. Only TCP is tested; UDP services such as WireGuard and Bedrock servers cannot be checked this way. Some providers block ports such as 25 and 445 on home lines. No answer does not prove a port is closed. Nothing is stored.
Related tools
What is my IP · TCP ping · Minecraft server status · All tools · Privacy