How to Read a Port Scan: Open, Closed and Filtered Ports Explained
2026-09-05 · undefined min
A port scan is one of the fastest ways to learn what a machine is actually doing on the network. Instead of guessing whether a service is running, it asks each of the 65,535 TCP ports the same question - are you listening? - and collects the answers. The output can look cryptic, but each of the three possible states tells you something precise about the machine.
The short version: open means something is listening, closed means nothing is there, and filtered means a firewall refused to answer. Most of the value of a scan is in reading that distinction correctly.
1981
TCP and ports are specified
RFC 793 defines TCP and its port-based multiplexing, establishing the 0-65535 port space and the idea that one host can run many services.
1990s
Port scanning becomes a diagnostic
Administrators start scanning their own networks to inventory services, while the same technique becomes a reconnaissance tool for attackers.
2000s
Firewalls and the filtered state
Stateful firewalls introduce the filtered result: a port that silently drops packets rather than rejecting them, hiding what is behind it.
Today
Scanning as routine hygiene
Regular scans of your own machines reveal forgotten services, misconfigured firewalls and ports that should have been closed long ago.
The three states and what each one means
Open means a service is listening on that port and answered the connection attempt. This is the state that matters most: something is reachable, and you should know what it is. It is not automatically bad - a web server on port 80 or 443 being open is expected - but every open port is a surface that could be probed.
Closed means the host answered but no service is listening there. The packet reached the machine and it said no. This is the reassuring result: it tells you the machine is reachable, the stack is alive, and there is simply nothing on that port.
Filtered: the firewall's silence
Filtered means the scan got no answer at all - no acceptance, no rejection. The most common cause is a firewall dropping packets silently, either to hide the port or as part of a default-deny policy. From the outside, a filtered port is indistinguishable from an unreachable host, which is often exactly what the administrator intended.
Because a filtered port gives no response, the scanner cannot tell whether a service is actually there. This is why a scan that shows many filtered results can still hide an active service behind a restrictive firewall - the state is information about the network, not about the host.
Which ports are normal to see open
Some ports are so common that seeing them open on a server is unremarkable. Port 22 (SSH), 25 (SMTP), 80 (HTTP), 443 (HTTPS) and 53 (DNS) are the everyday ones. A port list full of these is usually a healthy server, not an alarm.
The unusual ports are the interesting ones: high-numbered listening services, database ports like 3306 or 5432 exposed to the internet, or remote-management ports like 3389 (RDP) reachable from outside. Those are the ones worth investigating, because they expand the attack surface well beyond what the machine was intended to expose.
The risk scale: commonly-open ports are low risk, while unexpected exposed ports climb the scale.
When a port list should worry you
A scan is worrying when it reveals ports you did not know were open, or when services that should be internal-only are reachable from the internet. An open database, an unpatched management console, or a legacy service still listening years after it was retired are the patterns that matter.
Run a scan against your own machines as a periodic check rather than once in a panic. Changes in the port list - a new service appearing, an old one disappearing - are the clearest signals that something on the network has changed and should be reviewed.
要点总结
A port scan is only as useful as your ability to read it. Open means exposed, closed means absent, filtered means hidden. Scan your own systems regularly, know which ports are supposed to be open, and treat anything unexpected as something to investigate rather than ignore.
为防止滥用，请求会受到频率限制。此实例的运营者可以选择性地启用请求活动日志记录——如果启用，每次工具请求（您的 IP 地址、时间戳、使用的工具及输入的目标/查询内容）可能会被记录到数据库中，用于安全、防滥用和使用情况分析。此功能默认关闭。使用本网站即表示您同意上述条款；如果您不同意，请不要使用本网站。