termmap
Home › Features

A terminal front-end for nmap: what every button does

termmap is built around eight scans. Each maps to a documented nmap command line, shown in the output before it runs. Nothing is hidden and nothing is guessed.

Scanning from the toolbar

Pick a target in the Target field — a host, a range or a CIDR block. Fill Ports if the scan needs a list. Then press the scan. Tab moves between the output and the buttons; Enter runs the selected one or opens its dialog.

What each preset sends to nmap

The exact command lines, so you can copy them, change them or run them yourself:

ButtonCommandRootUse it for
Quicknmap -T4 -FNoTop 100 ports on a host or /24.
Deepnmap -T4 -A -v --version-lightPartlyVersions, scripts, OS and traceroute.
Pingnmap -snNoWhich hosts are up.
Portsnmap -p <list>NoA specific set: 22,80,443.
Svcnmap -sV --version-lightNoWhat answers on open ports.
OS / UDP / Scripts-O / -sU --top-ports 50 / -sCOS and UDPFingerprint, UDP services, default NSE scripts.

Controlling a running scan

nmap's stdout and stderr are streamed as they arrive, so a slow scan shows progress instead of a frozen screen. Esc stops the running scan and leaves the partial output in place, which is often the useful part.

How it compares

termmapraw nmapZenmap / wrappers
Runs over SSHYesYesNot without X11 or a web server
Visible scan buttonsYesNoYes
Exact command shownYesYesUsually hidden
Extra flagsOptions fieldEverythingVaries
Install footprint6.6 KB + nmapnmapGUI stack or web app
Config file or databaseNoneNoneProfile store or database
Maintained2026YesVaries
One file to readYesNoNo

What termmap does not do

  • Continuous monitoring or scheduling: one scan, then it exits.
  • Asset inventories and comparison between runs.
  • Non-interactive pipelines: script nmap directly.
  • Windows: the interface targets Linux, macOS and BSD terminals.