This article is Day 6 of a 180-day Kali Linux security course, teaching Nikto, an open-source web server vulnerability scanner that tests against a database of over 6,700 known security issues. The article explains what Nikto checks for, how to install and configure it, output formats for reporting, tuning options to focus scans, and how to triage findings by severity. Nikto complements directory discovery tools like Gobuster by auditing web servers for known vulnerabilities, misconfigurations, and outdated software in minutes rather than hours of manual inspection.
- Nikto's core function and detection scopeNikto tests servers against 6,700+ known security issues including server version disclosure and outdated software (e.g., Apache 2.4.49 mapping to CVE-2021-41773), missing security headers (X-Frame-Options, CSP, X-Content-Type-Options, Strict-Transport-Security), dangerous HTTP methods (PUT for file upload, DELETE, TRACE for XST attacks), exposed sensitive files (phpinfo.php, .htaccess, backup files), and default credentials on web management interfaces. Unlike Gobuster which discovers what paths exist, Nikto identifies what security problems exist at those paths.
- Operational noise and detection visibilityNikto sends thousands of HTTP requests in a short period, making it clearly visible in server logs and triggering IDS/WAF alerts on monitored systems. The article explicitly warns that it does not attempt stealth by default and advises scanning only authorized targets with explicit written permission. Evasion flags (-evasion 1-8) can reduce IDS signature matches but do not make Nikto invisible, and server logs will still record all requests.
- Output formats and professional reportingNikto supports five output formats: plain text (grep-friendly for quick analysis), HTML (readable client-facing reports), CSV (spreadsheet analysis and filtering), XML (import into Metasploit, Dradis, or other tools), and NBE (Nessus format). The article emphasizes always saving output via -o [filename] -Format [type] because scans take time to run and findings scroll past quickly in the terminal.
- Tuning categories for focused scanningThe -Tuning flag restricts scans to specific check categories (0–9 and a–c): category 0 (file upload), 1 (interesting files), 2 (misconfiguration), 3 (information disclosure), 4 (injection), 5 (path traversal), 6 (DoS), 9 (SQL injection), and b (software ID). The recommended combination for most engagements is -Tuning 123b to check misconfigurations, disclosure, and software without triggering DoS checks, or -Tuning x6 to exclude DoS entirely.
- Finding triage framework by severityCritical findings include dangerous HTTP methods (PUT/DELETE enabled), outdated software with active CVEs, and default credentials on web panels. High-severity items are exposed admin interfaces (phpMyAdmin, Tomcat Manager), directory indexing, and phpinfo.php accessibility. Medium severity includes HTTP TRACE enabled (XST vulnerability per OSVDB-877) and version disclosure. Low severity encompasses missing security headers and ETag inode leakage. The article provides grep commands to quickly filter each category from saved output.
- Authentication and proxy routing optionsNikto supports basic HTTP authentication via -id user:pass, cookie-based authentication with -cookie "PHPSESSID=...", and proxy routing through -useproxy to direct all traffic through Burp Suite for inspection. Custom User-Agent can be set to avoid default "Mozilla/... Nikto" identification. These options enable scanning behind login walls and through monitoring infrastructure.
- Multi-port scanning workflow integrationNikto can scan multiple ports in a single run (nikto -h TARGET -p 80,8080,8180,443) and supports HTTPS on standard and non-standard ports with -ssl flag. The article uses Metasploitable2 as an example where Apache Tomcat runs on port 8180 with default credentials (tomcat:tomcat) and exposes /manager/html for deploying arbitrary WAR files (remote code execution). The workflow sequence is Nmap (find services) → Gobuster (find paths) → Nikto (find vulnerabilities) → manual Burp testing.
- Nikto versus Gobuster complementary rolesGobuster brute-forces paths using wordlists to discover hidden content that exists; Nikto tests against known issues to find security problems. The article states both tools must be used together in professional assessments — Gobuster first to map attack surface, then Nikto to assess known vulnerabilities on discovered paths. Neither tool replaces the other; they cover different phases of reconnaissance.
Bottom line: Nikto is an essential automated web server vulnerability scanner that identifies known security issues, misconfigurations, and dangerous configurations in minutes, making it a critical early-stage tool in any authorized web application assessment when combined with Gobuster for content discovery. Proper use requires understanding its high network visibility, tuning scans to avoid out-of-scope checks like DoS, and triaging findings by severity to distinguish critical issues like exposed admin pan
Day 180 — Advanced Kali Mastery
Lab setup: Ethical Hacking Lab Setup at Home · Metasploitable Labs Hub
What Is Nikto and What Does It Check?
Nikto is an open-source web server scanner that tests against a database of over 6,700 known security issues. Unlike Gobuster which discovers hidden content by brute-forcing paths, Nikto checks specifically for known vulnerabilities, misconfigurations, and outdated software — matching the target server’s responses against a continuously updated database of security problems.
Install, Verify & Update Nikto
nikto -Version
– Nikto v2.1.6
# Install if missing:
sudo apt install nikto -y
# Update Nikto’s vulnerability database (do this before any scan):
nikto -update
# Downloads latest checks from CIRT.net
# Database location: /var/lib/nikto/databases/
# Show all available options:
nikto -Help
Basic Scan — Your First Nikto Results
Nikto’s core flag is -h (host). That is all you need for a basic scan against an HTTP target. Against your Metasploitable2 lab, this single command reveals a significant list of findings in under two minutes.
nikto -h http://192.168.56.101 # HTTP target
nikto -h https://target.com # HTTPS target
nikto -h 192.168.56.101 # IP (defaults to port 80)
nikto -h 192.168.56.101 -p 8180 # Specific port (Tomcat)
nikto -h 192.168.56.101 -p 80,443,8080,8443 # Multiple ports
nikto -h 192.168.56.101 -ssl # Force SSL/HTTPS mode
Output Formats — Saving Results for Reports
Always save Nikto output. The scan takes time to run and findings scroll past quickly in the terminal. Nikto supports five output formats — choose based on how you will use the results in your report or workflow.
nikto -h http://192.168.56.101 -o scan.txt # plain text
nikto -h http://192.168.56.101 -o scan.html -Format htm # HTML report
nikto -h http://192.168.56.101 -o scan.csv -Format csv # CSV (Excel)
nikto -h http://192.168.56.101 -o scan.xml -Format xml # XML (import to tools)
nikto -h http://192.168.56.101 -o scan.nbe -Format nbe # NBE (Nessus format)
# ─── Format use cases ─────────────────────────────────────────────
txt # Quick read, grep-friendly: grep “OSVDB” scan.txt
html # Readable client-facing output, include in report appendix
csv # Spreadsheet analysis, filter/sort findings by severity
xml # Import into Metasploit, Dradis, or other reporting tools
Tuning — Focus the Scan on What Matters
-Tuning restricts the scan to specific check categories. This is useful when you want faster scans, when certain check types (like DoS) are explicitly out of scope, or when you want to focus on a specific finding category during triage.
nikto -h http://192.168.56.101 -Tuning 123b # recon focus: misconfig + disclosure + software
nikto -h http://192.168.56.101 -Tuning 9 # SQLi checks only
nikto -h http://192.168.56.101 -Tuning x6 # run all EXCEPT DoS (x = reverse/exclude)
nikto -h http://192.168.56.101 -Tuning 4 # injection checks (XSS/CRLF) only
nikto -h http://192.168.56.101 -Tuning 2 # misconfiguration checks only — fastest
HTTPS & Custom Ports
nikto -h https://target.com # HTTPS auto-detected
nikto -h target.com -ssl -p 443 # Force SSL on port 443
nikto -h 192.168.56.101 -ssl -p 8443 # SSL on non-standard port
# ─── Metasploitable2 — multiple web services ─────────────────────
nikto -h 192.168.56.101 -p 80 # Apache (main web server)
nikto -h 192.168.56.101 -p 8180 # Apache Tomcat (Java app server)
nikto -h 192.168.56.101 -p 8080 # Additional web service
# ─── Scan multiple ports in one run ──────────────────────────────
nikto -h 192.168.56.101 -p 80,8080,8180,443
/manager/html — which allows deploying arbitrary WAR files (= remote code execution). Always scan non-standard ports that Nmap identifies as web services. First find them with Nmap, then scan with Nikto.Evasion Techniques — Reducing IDS Detection
In authorised engagements where the scope explicitly permits evasion testing, Nikto’s -evasion flag modifies HTTP requests to reduce the probability of IDS signature matches. These do not make Nikto invisible — server logs will still record the requests — but they may bypass signature-based IDS rules that look for Nikto-specific patterns.
1 Random URI encoding
2 Directory self-reference (/./)
3 Premature URL ending
4 Prepend long random string
5 Fake parameter
6 TAB as request spacer
7 Random case sensitivity
8 Windows directory separator (\)
# ─── Apply evasion during a scan ─────────────────────────────────
nikto -h http://192.168.56.101 -evasion 1 # random URI encoding
nikto -h http://192.168.56.101 -evasion 17 # encoding + random case
nikto -h http://192.168.56.101 -evasion 1234 # multiple techniques combined
Authenticated Scans — Scanning Behind Login Walls
nikto -h http://192.168.56.101 -id admin:admin
# ─── Cookie-based auth (use Burp to capture cookie) ──────────────
nikto -h http://192.168.56.101/dvwa/ \
-cookie “PHPSESSID=abc123; security=low”
# ─── Scan through a proxy (Burp Suite intercept) ─────────────────
nikto -h http://192.168.56.101 -useproxy http://127.0.0.1:8080
# All Nikto traffic routed through Burp — see every request/response
# ─── Custom User-Agent (change from default “Mozilla/… Nikto”) ──
nikto -h http://192.168.56.101 \
-useragent “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36”
Reading & Triaging Nikto Output — What Matters
Nikto outputs can be long. Knowing how to triage the findings quickly — which are critical, which are low-severity, which are false positives — is a skill that saves time in every engagement. Here is the priority framework:
grep -i “PUT\|DELETE\|upload” scan.txt # dangerous methods first
grep -i “admin\|phpmyadmin\|manager\|console” scan.txt # admin interfaces
grep -i “outdated\|appears to be” scan.txt # outdated software
grep -i “header\|missing” scan.txt # missing headers (low)
grep “OSVDB” scan.txt | wc -l # count total findings
Nikto vs Gobuster — Different Tools, Different Jobs
A common question from beginners is whether to use Nikto or Gobuster. The answer is always: both. They do fundamentally different things.
→
Gobuster
→
Nikto
→
Manual testing in Burp Suite
More on the information gathering workflow: Information Gathering Tools in Kali Linux | Penetration Testing Lifecycle Explained
📋 Nikto Command Reference Card — Screenshot This
nikto -h https://TARGET -ssl
nikto -h TARGET -p 8080,8443
nikto -update
nikto -h TARGET -o out.html -Format htm
nikto -h TARGET -o out.csv -Format csv
nikto -h TARGET -o out.xml -Format xml
nikto -h TARGET -Tuning x6 # skip DoS
nikto -h TARGET -Tuning 9 # SQLi only
nikto -h TARGET -Tuning 2 # misconfiguration
nikto -h TARGET -cookie “sess=abc”
nikto -h TARGET -useproxy http://127.0.0.1:8080
nikto -h TARGET -evasion 7 # random case
nikto -h TARGET -evasion 17 # encoding+case
grep -i “admin\|manager” scan.txt
grep -i “outdated” scan.txt
grep -i “header” scan.txt
Frequently Asked Questions – Nikto Tutorial
Nikto is one of the first tools I run against every web server in an authorised assessment — not because it finds sophisticated vulnerabilities, but because it finds the obvious ones in two minutes. Missing security headers. Outdated Apache. phpMyAdmin accessible from the internet. Tomcat Manager running on default credentials. These findings appear in reports from global financial institutions and small e-commerce sites alike. Nikto does not find everything — no automated tool does — but it finds the low-hanging fruit quickly, freeing your manual testing time for the vulnerabilities that require judgment to find.

