All free tools

Free tool

DNS & lookup

Port Checker

Probe a public hostname or IP on a TCP port. See open, closed, or timeout results for web, SSH, mail, and lab services.

Looks up public internet data for the target you enter. We do not store results.

Free tool

Knowing whether a TCP port answers from the internet separates firewall theory from reality. This free port checker performs a simple connect test from our servers to a public host so beginners, CCNA students, and network administrators can verify services such as 80, 443, 22, or 587. Use it after you place a server in a public CIDR block or publish an IPv4 example from subnetting practice—then confirm the port policy matches what you intended.

How to use the Port Checker

  1. 1

    Enter a public hostname or IP (private addresses are blocked).

  2. 2

    Choose a common port chip or type any port from 1 to 65535.

  3. 3

    Tap Check port to see open, closed, timeout, or error with latency.

Why port checks belong in troubleshooting

An ACL or NAT rule can look perfect in a Cisco networking lab and still leave a port filtered on the path. Helpdesk teams waste hours restarting apps when the real issue is a closed inbound port. This tool only performs a TCP connect—it does not grab banners or exploit services—so students can practise safe verification on home networks they expose carefully and on public demonstration hosts.

Common web port example

Check google.com on port 443. You should see an open result if the path allows HTTPS. Compare with port 22 on the same host; many web properties keep SSH closed to the world. That contrast teaches beginners what “open” really means.

Guides and next steps

Privacy note

We attempt a short TCP connection from our servers to the public host and port you enter. Private targets are blocked. We do not store results.

Frequently asked questions

Ready to go beyond free tools?

Live mentor-led courses turn calculator practice into real networking and IT skill.