⚡ Live · Real-Time · No Signup

Free Online TCP Port Scanner

Check open TCP ports on any domain or IP address in seconds. Real live connections — no mock data, no simulated results.

Real fsockopen connections Banner grabbing Security recommendations
Quick presets (max 100 ports per scan):
Scanning…

Scan Results

Advanced Scanner Features

Built for developers, sysadmins, and security teams who need fast, accurate answers.

Real-Time Live Scanning

Every result comes from a genuine TCP connection attempt — no cached or simulated data.

Security Recommendations

Get actionable guidance on risky open ports like Telnet, RDP, MySQL, and Redis.

Service Banner Grabbing

Optionally capture service banners to identify software versions running behind a port.

Preset Port Groups

One-click scans for Web, Mail, Database, and Remote-Access port groups.

Custom Ranges

Scan single ports, comma lists, or ranges like 1-1024 in a single request.

Export Reports

Copy or download your scan results as a plain-text report for records or tickets.

How the TCP Port Scanner Works

Three simple steps to a live network diagnostic.

1

Enter host & ports

Type a domain or IP address and choose a preset or custom port list.

2

We connect live

Our PHP backend opens a real TCP socket to each port using fsockopen.

3

Review & export

See open/closed status, latency, and service names — then copy or download.

What Is a TCP Port Scanner and Why Does It Matter?

A TCP port scanner is a diagnostic tool that checks whether specific network ports on a server respond to connection attempts. Every internet service, from a website on port 443 to a database on port 3306, listens on a numbered port, and knowing which of those doors are actually open from the outside world is one of the most basic yet powerful ways to understand your own exposure. Instead of guessing whether a firewall rule works or a service is reachable, a live scan gives a direct, verifiable answer in seconds.

Our online port checker works by opening a genuine TCP connection to each requested port using PHP's fsockopen function, the same low-level approach system administrators have relied on for decades. There is no mock output and nothing pre-generated: when a port replies, it is marked open; when the connection times out or is refused, it is marked closed. This straightforward, honest approach is what makes the tool useful for real troubleshooting rather than just a demo.

People turn to a TCP port checker for a handful of common reasons. Developers use it after deploying a new application to confirm the correct port is actually listening publicly. System administrators use it to audit servers for accidentally exposed services, such as a database or remote desktop port that should never face the internet. Security-conscious teams run periodic scans as part of routine hardening, checking that only the ports required for business functions — typically HTTP, HTTPS, SSH, and mail — remain accessible, while everything else stays closed or filtered.

Using the scanner is simple: enter a hostname or IPv4 address, pick a preset such as Common Ports, Web, Mail, Database, or Remote Access, or type a custom list like 22,80,443 or a range like 1-1024, then click Scan Ports. Within moments the results table shows each port's status, an estimated service name, the response latency, and — if banner grabbing is enabled — any text the service reveals about itself. This last detail can be particularly useful for spotting outdated software versions that may carry known vulnerabilities.

It is worth remembering that an "open" result simply means a TCP handshake succeeded; it does not automatically mean a service is misconfigured or unsafe. Many ports, like 80 and 443, are meant to be open on a public web server. The real value comes from comparing what the scan finds against what you expect to be running. If a port you never configured shows as open, that is a signal worth investigating immediately, whether it points to a forgotten test service, a misapplied firewall rule, or something more concerning.

Finally, always scan responsibly. Only test hosts and IP addresses you own or are explicitly authorized to assess. Unauthorized scanning of third-party infrastructure can violate acceptable-use policies and, in many jurisdictions, computer misuse laws — so treat this tool as part of your own security workflow, not as a way to probe systems that are not yours.

Frequently Asked Questions

Enter your server's hostname or public IP address in the scanner above, add the port number (for example 22 for SSH or 3306 for MySQL), and click Scan Ports. The tool opens a real TCP connection and reports whether the port responds as open or closed within seconds.
A port can appear closed if a firewall, security group, or router is blocking inbound traffic even though the local service is listening. Check your server firewall rules, cloud security groups, and router port forwarding, since the scan reflects what's reachable from the public internet, not just what's running locally.
You should only scan hosts and IP addresses you own or have explicit written permission to test. Scanning third-party systems without authorization may violate computer misuse laws and acceptable use policies, so always confirm ownership or consent first.

Explore More Free Diagnostic Tools

From DNS lookups to SSL checks, SEOWebChecker gives you everything to keep your infrastructure healthy and secure.