Menu

An Open Port Doesn’t Mean a Vulnerability — Understanding Nmap Results
📰

An Open Port Doesn’t Mean a Vulnerability — Understanding Nmap Results

DEV Community: github·Radz-04·4 days ago
#2LPC3AjB
#devtogithub#technology#devto#dev#nmap
Reading 0:00
15s threshold

When I started studying penetration testing, I spent a lot of time learning Nmap commands.

But knowing how to run a scan and understanding its results are two different things.

One of the most important distinctions is how Nmap classifies ports.

Open, closed, and filtered

Let’s take a simple TCP Connect scan:

nmap -sT -p 22,80,443 127.0.0.1

This scans three TCP ports on your own computer.

Depending on which services are running, Nmap might return something like:

PORT STATE SERVICE

22/tcp open ssh

80/tcp closed http

443/tcp filtered https

This is an illustrative output, not the result of an actual scan.

Here’s what those states mean:

Open: A service is accepting connections on that port.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.