Toolsky

Free Online Tools & Utilities for Every Task.

Open Port Checker

The open port checker is a tool you can use to check your external IP address and detect open ports on your connection.

21
FTP
22
SSH
23
Telnet
25
SMTP
53
DNS
80
HTTP
110
POP3
143
IMAP
443
HTTPS
3306
MySQL
5432
PostgreSQL
8080
HTTP Proxy

You have set up the game server, forwarded the port in your router, and your friends still cannot connect. Is the port actually reachable from the internet, or is something quietly blocking it? This open port checker tests your connection from the outside: it reports your external IP address and probes the port you specify to see whether the internet can reach a service listening behind it.

What an Open Port Really Means

A port is a numbered channel — from 0 to 65535 — that lets one device run many network services at once. Web traffic rides 80 and 443, email servers listen on 25, game and application servers often pick their own. Your router uses NAT to share one public IP address among every device at home, so an incoming connection only reaches the right machine if a port forwarding rule points it there and the device itself is listening and not blocking it with a firewall.

An external check is the only honest test, because from inside your own network many things appear to work that are invisible from outside. The checker connects (or attempts to connect) from a remote server to your public IP on the chosen port — the same path a friend's game client or a customer's browser would take.

What This Checker Tells You

  • Your current external (public) IP address as the internet sees it
  • Whether a specified TCP port on that address accepts connections from outside
  • A fast verdict you can repeat after every change to router or firewall settings
  • A way to test common service ports as well as custom application ports

If you need to identify the address itself, What's My IP goes deeper on your connection details, while the ping tool tests basic reachability and latency to a host.

How to Check a Port

  1. Make sure the service you are testing — game server, camera, application — is actually running on the target device.
  2. Note your external IP address as shown by the tool; it is filled from your current connection.
  3. Enter the port number you want to test.
  4. Run the check and read the result: open means a connection was accepted, closed or timed out means it was not.
  5. If the result is closed, work through your setup (see the tips below) and test again after each change.

A Worked Example: The Game Server That Nobody Could Join

A typical case: a player hosts a game on the default port 25565. The server software is running, and the router has a forwarding rule pointing 25565 to the PC's local address, 192.168.1.50. The checker still reports the port closed. Working through the chain reveals the culprit — the PC's own firewall was blocking the game's executable, so connections arrived at the machine and were refused there. One firewall exception later, the same check reports open, and friends connect. The lesson: "closed" tells you the chain is broken, and the chain has three links — service running, router forwarding correct, and local firewall allowing.

Tips, Limitations and Common Mistakes

The most common mistake is testing while the service is stopped; nothing can answer on a port where nothing listens, so the result will always read closed. Second is forwarding to the wrong internal address — if your PC's local IP changed because DHCP gave it a new one, the router may be forwarding to a device that no longer exists at that address. Reserve a static local IP for hosts you forward to. Third, some internet providers place customers behind carrier-grade NAT, in which case no amount of router configuration will open a port, because your public address is shared; the checker will show an address that does not match your router's WAN address, which is the tell-tale sign.

Protocol matters too. This style of test probes TCP connections. Services that use only UDP (some games and voice apps) need a UDP-specific test, and a "closed" TCP result says nothing about their UDP state. Finally, treat openness deliberately: every open port is a door the whole internet can knock on, so forward only what you use, keep the service updated, and remove rules when you stop hosting.

Frequently Asked Questions About the Open Port Checker

Why does my port show closed when I forwarded it?

One of the three links is broken: the service is not running, the router forwards to the wrong internal IP or port, or a firewall (on the router or the device) is blocking it. Fix and retest one change at a time.

What is my external IP address?

It is the public address your internet provider assigns to your connection, shared by all devices behind your router. The checker displays it automatically.

Is it safe to have open ports?

An open port is only as safe as the service behind it. Keep hosted software updated, use strong passwords where relevant, and close forwards you no longer need.

Can this tool check UDP ports?

This check tests TCP reachability. UDP has no connection handshake, so it needs a different testing method; a closed TCP result does not describe the UDP state.

Why does the checker show a different IP than my router does?

That usually indicates carrier-grade NAT at your provider: your router's WAN address is a private address, and the true public address is shared. Port forwarding will not work until the provider gives you a public address or IPv6 is used.

Which port does a normal website use?

Standard web traffic uses port 80 for HTTP and 443 for HTTPS. Testing those on your own host tells you whether a local web server is reachable from outside.

Does an open result guarantee my friends can connect?

It proves the internet can reach the service, which is the usual blocker. Remaining problems would be inside the application itself, such as version mismatches or server settings.

Test From the Outside, Fix With Confidence

Guessing at network problems wastes hours. One external check tells you whether the internet can reach your service, and each retest confirms whether your last fix actually worked — turning a vague "it doesn't connect" into a short, solvable checklist.