No Signup Unlimited Usage Real Data 100% Free Privacy First Fast Results Export Reports Mobile Friendly

Port Checker

Check whether ports on your own connection are open to the internet: up to 10 TCP ports per run (80, 443, 22, 3389, 25565, 27015…) tested from our server with a 3-second timeout and reported as open, closed or filtered. Only your own IP can be tested.

Fetching live data…

Quick answer

The Port Checker tells you whether a port on your own internet connection can be reached from outside. It is the quickest way to confirm that port forwarding works for a game server, a security camera, a home NAS, Plex or remote desktop — or, the other way round, that a service you never meant to publish is not exposed. Pick up to ten ports, run the check, and our server tries to open a TCP connection to each of them on the address you are connecting from.

How it works

  1. The tool takes the public IP address your request arrived from. You cannot type another address, so it can only ever test your own connection.
  2. Type ports or tap the quick buttons — 80, 443, 21, 22, 25, 3389, 8080, 25565 (Minecraft), 27015 (Steam), 32400 (Plex) and more. Ranges such as 8080-8085 work too, up to ten ports per run.
  3. Our server attempts a TCP handshake with every port at the same time and waits at most three seconds for each.
  4. Each port is reported as open, closed or filtered, with the service usually found on it and a warning for ports that are risky to leave open.

What the results mean

  • Open — the handshake completed: a program is listening and the port is reachable from the internet.
  • Closed — your router or computer answered with a refusal. The path is open but nothing is listening, often because the program is not running.
  • Filtered — no answer within three seconds. A firewall is dropping the connection, the port is not forwarded through your router, or your provider blocks it.
  • Risky ports — open Telnet, SMB, RDP, VNC or database ports (MySQL, PostgreSQL, Redis, MongoDB) are flagged, because they are constantly scanned and attacked.

Why it matters

Port forwarding fails silently: the router rule looks right, but friends still cannot join your server. Testing from outside your network is the only reliable check, because a test from inside often succeeds through the router’s loopback even when the outside world is blocked. Just as important is the opposite case — a forgotten remote-desktop or database port open to the whole internet is one of the most common ways home and small-office machines get compromised.

Fixing a port that should be open

Make sure the program is running and listening on that port, give the device a fixed local IP, and forward the port on your router to that address. Allow the port in the device’s own firewall too — Windows Defender Firewall blocks new inbound ports by default. If it still shows as filtered, your provider may use CGNAT, where many customers share one public address: compare the address shown by What Is My IP? with the WAN address in your router. If they differ, ask your provider for a public IP. Checking a server’s reputation instead? Try the IP Blacklist Checker.

Frequently asked questions

Why can I not test another IP address?

Testing ports on someone else’s address is port scanning, and many networks treat it as an attack. Limiting the tool to the address you connect from keeps it useful for checking your own setup and useless for probing others. Each address also has a strict limit on how many checks it can run.

Can it test UDP ports?

No. UDP has no handshake, so a silent UDP port looks the same whether it is open or blocked. Services that only use UDP, such as WireGuard and many game voice channels, will show as filtered even when they work.

I use a VPN. Which address is tested?

The VPN’s. Our server sees the VPN’s exit address and tests that. Disconnect the VPN to test your home connection, or open the matching port in your VPN provider’s port-forwarding settings if it offers them.

Learn & Resources

Guides, tips and tutorials hand-picked for this tool — go from running a check to actually fixing it.