Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Nikto?

Nikto is an open-source web server scanner that checks for thousands of known dangerous files, outdated server versions, and insecure configuration items.

Illustration for the cybersecurity term Nikto
Home / Blog / Cybersecurity Terms / What Is Nikto?
17 November 2026

What Is Nikto?

What Is Nikto?

Nikto is a web server scanner written in Perl by Chris Sullo and distributed through CIRT.net. It connects to a web server and works through a database of several thousand checks: files and scripts that are known to be dangerous or that should not be publicly reachable, server software versions with published vulnerabilities, default installations left in place, and configuration items that indicate a problem.

It has been around since 2001 and it still ships in Kali Linux, which says something about how persistent the problems it finds are. A scanner that looks for forgotten administrative scripts and default installations should have become obsolete long ago, and it has not.

What It Checks

Output can be written as HTML, CSV, XML, or in formats other tools consume, which makes it straightforward to fold into a larger workflow.

It Is Deliberately Loud

Nikto makes no attempt at stealth. It sends thousands of requests with a recognisable user agent, it does not randomise timing by default, and any competent monitoring will see it immediately. That is not a defect; it is a design decision from a tool intended for authorised assessment and for quick triage of a server you administer.

For defenders this makes it a reasonable test of your own detection. If a Nikto scan against your public web estate produces no alert anywhere, the problem is not that the tool is noisy. It is that nobody is listening, and a quieter attacker will certainly go unnoticed.

Where Its Limits Are

This is the part that matters most, because Nikto is frequently misrepresented as a web application scanner. It is not one.

It checks the server and what sits in its document root. It does not understand your application. It will not find SQL injection in a parameter it has never seen, cross-site scripting in a form it cannot fill in, broken authorisation between two users, or any business logic flaw. It cannot authenticate meaningfully, crawl a single-page application, or follow a multi-step workflow.

For those, you need an application scanner such as OWASP ZAP or Burp Suite, and beyond that a human. A report built from Nikto output alone is a configuration check with a misleading title.

Its check database also ages. Many entries target software from the 2000s, which generates results that need interpretation rather than transcription. And like any version-based scanner, it reports vulnerabilities inferred from a banner, so a backported security fix in a Linux distribution package produces a false positive routinely.

Nikto and Nuclei

The natural modern comparison is with Nuclei, which does similar work with a different model. Nuclei uses community-maintained YAML templates, updated continuously, often within hours of a vulnerability being published, and it is considerably faster. Nikto’s database is maintained by a smaller group and moves more slowly, but it includes a long tail of historical checks that nobody has written a template for.

Most testers run both, along with content discovery using Gobuster or ffuf, and treat all three as the automated layer beneath manual testing.

What Defenders Should Do

Remove what it looks for. Delete installer scripts, sample applications, and documentation directories after deployment. Keep backups out of the web root entirely. Disable directory indexing and the TRACE method. Suppress version banners, which is cosmetic but removes the easiest version-based findings. Add the standard security headers. Decommission old application versions rather than leaving them reachable.

Then monitor for the scan itself. A high volume of 404 responses from one source, and any request for a path that only a scanner would try, are among the easiest and highest-confidence web alerts to configure. A web application firewall will block the default configuration outright, which is worth having, as long as it is not mistaken for a reason to leave the underlying files in place.

At Privia Security, our Web Application Security Services combine server-level scanning with manual application testing and report the two separately.

FAQ – Frequently Asked Questions

Is Nikto a Web Application Scanner?

No, and the distinction matters. It checks the web server and its document root for dangerous files, outdated versions, default content, and configuration problems. It does not test application logic, so it will not find SQL injection in an unknown parameter, cross-site scripting in a form it cannot complete, or authorisation flaws between users. Those need an application scanner and a human.

Why Is Nikto So Easy to Detect?

It was designed for authorised assessment, so it makes no attempt at stealth: thousands of requests, a recognisable user agent, and no timing randomisation by default. That is useful for testing your own monitoring. If a Nikto scan of your public estate generates no alert anywhere, a quieter scanner will certainly pass unnoticed.

Should We Use Nikto or Nuclei?

Both, since they overlap less than their descriptions suggest. Nuclei is faster, template-driven, and updated by the community within hours of a vulnerability being disclosed. Nikto’s database moves more slowly but carries a long tail of historical checks that nobody has written a Nuclei template for. Run them alongside content discovery as the automated layer.

How Do We Reduce What It Finds?

Remove installer scripts, sample applications, and documentation directories after deployment, keep backup files out of the web root entirely, disable directory indexing and the TRACE method, suppress version banners, add the standard security headers, and decommission old application versions rather than leaving them reachable on the same host.

Related Terms

You May Be Interested In These

What Are CRL and OCSP?

Cybersecurity Terms

17 November 2026

What Are CRL and OCSP?

Read More
What Is Software-Defined Radio?

Cybersecurity Terms

17 November 2026

What Is Software-Defined Radio?

Read More
What Skills Does an OT Security Engineer Need?

Cybersecurity Terms

17 November 2026

What Skills Does an OT Security Engineer Need?

Read More