CEH · M03

Port states: what do open, closed and filtered tell you?

A scan result is an observation made at a particular time, vantage point and with a particular method. Interpret the response before choosing an authorized follow-up.

After this lesson, you can
  • Explain differing results using observation conditions.
  • Avoid equating an open port with a vulnerability or compromise.

Prerequisites: Reconnaissance notes: separate observation from inference

States describe what the probe can observe

In Nmap terminology, open indicates an application accepting the relevant connections or data. Closed indicates reachability without a corresponding listener. Filtered means packet filtering prevents a determination of whether the port is open. Read the state together with the probe protocol.

A combined state such as open|filtered preserves uncertainty; do not silently discard “filtered.” A tool’s state is not an immutable host property. Vantage point, time, filtering and method can affect the result.

Further reading: Nmap: Port Scanning Basics

Separate four steps in the evidence chain

Separate network reachability, port state, service identification and verification of a particular resource, configuration or weakness. Each step requires its own response evidence. A later conclusion does not arise automatically from an earlier label.

For example, 443/tcp open supports the presence of a listener in that observation. It has not verified website identity, TLS configuration or application authorization. Record port, protocol, time, vantage and method before comparing runs.

Example: different internal and external views

At 10:00, a synthetic host is observed as 445/tcp open from one test network and filtered from an external test network.

The results are compatible with path-based access controls, but rules and packet evidence are needed to confirm the cause. They do not by themselves indicate a broken tool or prove that the external view has no service.

Conclusion: Keep both vantage points and check the authorized control configuration.

Offline exercise: bound a scan summary

Read the synthetic output only; do not run a scan.

  1. Create three rows: 22/tcp closed, 443/tcp open and 53/udp open|filtered.
  2. Write one supported observation and one unsupported conclusion for each row.
  3. Add time, source network and method fields to 443; mark missing values unknown.

Expected result

53/udp is not definitely open; 443 does not establish a secure website; 22 closed does not mean the host is absent.

Check your work

Can you explain why the three rows cannot be counted as three vulnerabilities?

Finish and clean up

Save the text summary; no system state was changed.

Q&A · Check your reasoning

Choose an answer and confidence, then read every explanation. Answers stay in this browser.

ceh-m03-port-q1 · Original practice

What does 443/tcp open directly support?

What does 443/tcp open directly support?
ceh-m03-port-q2 · Original practice

How should open|filtered be recorded?

How should open|filtered be recorded?
ceh-m03-port-q3 · Original practice

What should be retained when comparing scans?

What should be retained when comparing scans?

Connect the next idea

Terms: Port state·Evidence boundary

Sources & scope

These sources support the technical principles. Examples, questions and exercises are original to this series.