Max 20 ports per scan, 5 scans per minute. For bulk scanning, use a local network diagnostic tool.
| Port | Service | Status | Response |
|---|
Your All‑In‑One Online Tool Hub
Instantly test whether TCP ports are open, closed, or filtered on any IP address or hostname. Use preset groups for common services or enter your own ports — results show service name, status, and response time.
Max 20 ports per scan, 5 scans per minute. For bulk scanning, use a local network diagnostic tool.
| Port | Service | Status | Response |
|---|
These are the three states a TCP port can return. Open means a service is actively listening on that port and accepted the connection — the port is reachable and in use. Closed means the target host responded but no service is running on that port — the port exists but nothing is listening. Filtered means a firewall, router, or network device blocked the probe entirely and returned no response. Filtered does not tell you whether a service is running — it just means something in the path is blocking access to that port.
Port forwarding tells your router to send incoming traffic on a specific port to a device on your internal network. For example, forwarding port 25565 to your gaming PC lets friends connect to your Minecraft server. To test it, enter your public IP address as the target, enter the port you forwarded, and click Scan Ports. If the result shows Open, forwarding is working correctly. If it shows Closed or Filtered, check your router settings, confirm the service is running on the target device, and verify your local firewall is not blocking the port.
Filtered means a firewall dropped the probe packet without sending any response. This is intentional behavior on well-secured networks — by not responding at all, the firewall gives no information to a potential attacker about what is or is not running behind it. A Closed result means the host actively replied to say nothing is listening. Filtered is generally the more secure response, but it can also appear when there is a routing problem, a stateful firewall is blocking new connections, or your ISP is filtering that port.
This tool is intended for use on servers and IP addresses you own or are authorised to test. Scanning ports on systems without permission may be illegal in your jurisdiction and violates the terms of service of most hosting providers. Use this tool responsibly — for diagnosing your own servers, verifying your firewall rules, and testing port forwarding on your own network.
Several things can cause a port to appear Filtered even when you expect it to be open. A firewall on the target server itself may be blocking external probes even though the service is running. An upstream firewall or router may be filtering the port before traffic reaches the server. Some ISPs block specific ports at the network level. Cloud providers often have their own firewall layers — security groups, network ACLs — that must be configured separately from the server's own firewall. Check all layers in order: ISP, cloud provider firewall, router, host firewall, and then the service configuration itself.
Disclaimer: QuickITTools.com and EnterPlanet LLC provide this port checker for authorised diagnostic use only. Only scan IP addresses and servers you own or have explicit permission to test. Port scanning systems without authorisation may be illegal in your jurisdiction. Results reflect real-time TCP connection attempts from the QuickITTools API server and may differ from scans conducted from other locations or networks.