Global probes
Confirm connectivity from a neutral network to rule out local firewall rules or ISP filtering.
Port Checker is the dedicated port checker for SRE, DevOps, and security engineers to validate connectivity, share common port checker knowledge, and respond to outages faster. This port checker keeps your investigations focused on the exact services that matter.
Enter an IP address or hostname with a target port to verify connectivity from our cloud-based port checker probe.
Always confirm you have permission before scanning or testing endpoints you do not own.
Instant port testing
Modern operators need fast answers. Port Checker combines live port checker testing, best practices, and documentation in one place so the port checker workflow stays consistent for every team member.
Confirm connectivity from a neutral network to rule out local firewall rules or ISP filtering.
Each featured port includes setup checklists, troubleshooting flows, and security reminders.
Crafted for on-call teams with responsive design, dark mode, and multilingual support.
How it works
The test runs from an external network, so it shows whether a service is reachable from the public internet rather than only from your local machine.
Provide a public IP address, IPv6 address, or hostname and the TCP port you want to check.
Port Checker sends a TCP connection attempt from a cloud probe, similar to how a remote client would reach your service.
A successful handshake means the port is open. A rejection, timeout, or blocked packet points to a closed or filtered path.
Use the result to verify port forwarding, firewall changes, cloud security groups, and service availability.
Result meanings
A port check is a point-in-time connectivity test. Read the status with your firewall, router, ISP, and application configuration in mind.
The target accepted a TCP connection on that port.
Confirm the exposed service is expected, patched, authenticated, and monitored.
The host was reachable, but nothing accepted the connection on that port.
Check whether the service is running, listening on the right interface, and allowed through the firewall.
Packets were dropped or blocked, so the exact port state could not be confirmed.
Review router forwarding, security groups, ACLs, ISP filtering, CGNAT, and source-IP allowlists.
Instant port testing
Jump straight into the guides for the ports Port Checker users ask about most often, then run a port checker against each service to confirm availability.
Encrypt web applications with TLS certificates on port 443.
Transfer files securely through SSH tunnels.
Manage servers remotely with encrypted shell access.
Serve file shares and authentication over TCP.
Serve web traffic without encryption on port 80.
Legacy plaintext remote console access.
Provide name resolution for infrastructure.
Monitor infrastructure with SNMP polling and traps.
Set up VoIP signaling on SIP ports.
Connect to remote desktops with VNC on port 5900.
Provide Windows remote desktop access.
Distribute precise time to fleet devices.
Test reachability and latency with ICMP echo.
Expose internal apps through reverse tunnels.
Host multiplayer Minecraft worlds.
Serve classic file transfers on ports 20/21.
Retrieve email messages from servers.
Expose relational databases to applications.
FAQ
Get clarity on how port forwarding works, how to interpret Port Checker results, and why some ISPs block certain ports.
Port forwarding maps an external port on your router or firewall to an internal service. It enables access from the internet to devices on private networks.
Consumer ISPs often block ports such as 25, 80, or 445 to limit malware and spam. Contact your provider about business plans if you need them opened.
Verify ports after network changes, firewall updates, or security incidents. Automate recurring checks for mission-critical services.
External checks can be blocked by firewalls, cloud security groups, ISP filtering, geo rules, or source-IP allowlists. Verify the full path from the internet to your service and compare with an internal test.
Open means the target accepted a connection on that port. Closed means the host was reachable but that port was not accepting connections. Filtered means packets were blocked or dropped by a firewall or ACL, so the exact state cannot be confirmed.
We process the host and port you submit to run checks and keep limited technical logs for reliability and abuse prevention. See the Privacy Policy for details on retention and handling.
No. This tool is best for point-in-time diagnostics. For production systems, pair it with continuous monitoring, service health metrics, and alerting.