How this is verified

What "checked" means

Each documented command is taken apart and compared with the tool it names:

• Ran the real release. The tool was installed and its own --help output was compared with every flag and subcommand on the page.
• Read the source. For tools that cannot run here, the option definitions or function names were read from the project's source.
• Upstream docs. For Windows-only tools, flags and actions were compared with the project's README.
• Not checked. Graphical tools, or tools with nothing to check on the command line.

What it does not prove

• That every line is covered. General shell commands (ls, curl, chmod), output samples and anything the checker could not parse were skipped. The count above is commands actually checked.
• That a command works against your target. Example IPs, paths, wordlists and credentials are placeholders.
• That the explanations are right. This checks option names and mode numbers, not the teaching text. A flag can exist and still be the wrong choice.
• That newer releases have not changed since the date above. Tools rename flags often, and the example pages say which release they were checked against.
• That simulator output is real. The simulator uses scripted scenarios, not live tools.

Mistakes this caught

The first pass found these in the pages as originally written. They are fixed.

Every tool

Found something wrong?

Please open an issue with the page, the command and what you saw. Corrections are added to the list above.