Reading a port scan properly

A scan answers one narrow question: which ports will accept a connection. This set checks that you can read the answer, tell the states apart, and keep the target on your own device.

4 questions 1 task Read the lesson

Questions

Each one is marked as you go, and the explanation arrives straight after, which is the part worth reading.

4 questions, marked as you go.

1 In an nmap table, which column answers whether a port will accept a connection?
2 What does it mean when a port shows as closed?
3 Why is it acceptable to run nmap against localhost but not against a host you do not own?
4 In a scan of many ports, what does the line Not shown: 99 closed tcp ports mean?

Tasks

These need your own device. Run the command in Termux, then paste what it printed. The marking looks at what the output means, so spacing, version numbers and ordering do not matter. If you have not installed anything yet, the lesson covers the setup.

Scan a few ports on your own device

This scans four named ports on localhost, which is your own device and nothing else. The -n flag keeps it local by skipping name lookups. Paste the whole scan output.

Run this in Termux On your own device. Nothing on this page executes it. The command runs in your terminal, and this box only reads what you paste back.

nmap -n -p 22,80,443,8022 localhost
Marking your own work Both halves of this are checked in your browser, with no server involved, so nothing stops you from pasting output you did not run. The tasks are written so that the easiest way to pass one is to actually do it and read the result, which is the whole intention.

All sets Read the lesson