Port Scanner

TCP probes against common port groups — only for targets you own or are authorized to test.

What a port check does

A TCP connect probe tells you whether a service is listening on a port: 80/443 for web, 25/465/587 for mail, 3306/5432 for databases, 22 for SSH. Open ports are your attack surface — every one should be intentional, firewalled and patched.

Authorization matters

Port scanning hosts you do not own can violate terms of service and local law. This tool requires an explicit authorization confirmation and only probes common service port groups — use it on your own servers.

Closed vs filtered

A closed port answers with RST (nothing listens). A filtered port gets no answer at all — a firewall dropped the packet. From the outside, filtered is what you want for services that must not be public.

Need the in-depth Chinese version? Read the full guide.

Related articles

More in the blog index

Frequently asked questions

Why does the scan require confirmation?

To ensure you only scan targets you own or are authorized to test. Unauthorized port scanning is illegal in many jurisdictions.

My port shows closed but the service works?

If a service only binds to localhost or a private interface, it is invisible from outside — that is correct behavior for databases. Public web ports failing while the site works may indicate geo-blocking of our scanner IP.

How fast is the scan?

Common port groups complete in a few seconds. This tool is intentionally limited to service groups rather than all 65535 ports.