Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Intro Reference Guide Book Install Guide
Download Changelog Zenmap GUI Docs
Bug Reports OS Detection Propaganda Related Projects
In the Movies In the News

Command-line Options

Being a graphical application, most of Zenmap's functionality is exposed through its graphical interface. Zenmap's command-line options are given here for completeness and because they are sometimes useful. In particular, it's good to know that the command zenmap <results file> starts Zenmap with the results in <results file> already open.

Synopsis

zenmap [ <options> ] [ <results file> ]

Options Summary

-f, --file <results file>

Open the given results file for viewing. The results file may be an Nmap XML output file (.xml, as produced by nmap -oX) or a Umit scan results file (.usr). This option may be given more than once.

-h, --help

Show a help message and exit.

-n, --nmap <Nmap command line>

Run the given Nmap command within the Zenmap interface. After -n or --nmap, every remaining command line argument is read as the command line to execute. This means that -n or --nmap must be given last, after any other options. Note that the command line must include the nmap executable name: zenmap -n nmap -sS target.

-p, --profile <profile>

Start with the given profile selected. The profile name is just a string: "Regular scan". If combined with -t, begin a scan with the given profile against the specified target.

-t, --target <target>

Start with the given target. If combined with -p, begin a scan with the given profile against the specified target.

-v, --verbose

Increase verbosity (of Zenmap, not Nmap). This option may be given multiple times to get even more verbosity.

Error Output

If Zenmap happens to crash, it normally helps you send a bug report with a stack trace. Set the environment variable ZENMAP_DEVELOPMENT (the value doesn't matter) to disable automatic crash reporting and have errors printed to the console. Try ZENMAP_DEVELOPMENT=1 zenmap -v -v -v to get a useful debugging output.

On Windows, standard error is redirected to a file zenmap.exe.log in the same directory as zenmap.exe, instead of being printed on the console.

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]