Free Penetration Testing Tools: What to Use
The best free penetration testing tools for a small site are ZAP for web scanning, Burp Suite Community for manual poking, Nmap for network checks and WPScan for WordPress.
Run them only on sites you own or have written permission to test, and bring in a person when you need to know what an attacker could really do.
This post is for owners and small teams who want a list of tools they can act on today. You will get a table that sorts the tools by job, copy-pasteable commands, a clear line between safe and risky, and a plain guide to when free tools stop being enough.
What a free pentest tool really is
A penetration test (pentest) is a controlled attempt to break into a system so you can find weak spots before a criminal does. Tools help with that job, but most free ones are scanners. A scanner is software that checks your site against a list of known problems and reports matches.
Two terms are worth knowing:
- Open source means the code is public, so anyone can read it and check what the tool does. Most of the tools below are open source.
- Free only means no price. Burp Suite Community is free but not open source.
A scanner is fast and cheap. It does not think like an attacker, and that gap matters later in this post.
Free pentest tools by job
Here is the short list, sorted by what each tool does.
| Job | Tool | Cost and licence | What it does | Skill needed |
|---|---|---|---|---|
| Web scanning | ZAP | Free, open source | Crawls your site and flags common web flaws | Low to medium |
| Web scanning | Nikto | Free, open source | Checks a web server for outdated software and risky files | Low |
| Web scanning | Nuclei | Free, open source | Runs community templates for known issues | Medium |
| Proxy | ZAP | Free, open source | Sits between browser and site so you can read and edit traffic | Medium |
| Proxy | Burp Suite Community | Free, not open source | Manual traffic inspection and replay (no automated scanner in this edition) | Medium to high |
| Network | Nmap | Free, source available | Finds open ports and the services behind them | Low to medium |
| Network | Greenbone Community Edition (OpenVAS) | Free, open source | Scans servers for known vulnerabilities | Medium |
| CMS | WPScan | Free for non-commercial use, API token has limits | Finds outdated WordPress core, plugins and themes | Low |
| HTTPS setup | testssl.sh | Free, open source | Checks your HTTPS and certificate settings | Low |
For a first pass, start with ZAP, Nmap and (on WordPress) WPScan.
Web scanners: ZAP, Nikto and Nuclei
ZAP (Zed Attack Proxy) is the most beginner-friendly option. It is maintained as an open-source project and has a safe mode called the baseline scan. The baseline scan watches normal responses and reports issues such as missing security headers. It does not attack your site.
If you have Docker installed, run:
docker run --rm -t ghcr.io/zaproxy/zaproxy:stable zap-baseline.py -t https://yourdomain.com
Read the output top to bottom. Treat any FAIL as a priority. By default most findings show as WARN, so read those too.
Nikto is a quick command-line check for old server software and leftover files:
nikto -h https://yourdomain.com
Nikto is noisy. It sends many requests, including injection-style checks, so it is an active scanner. It shows up in logs and gives some false alarms. Run it on a staging copy of your site (a private duplicate used for testing), or on your live site only with a backup and during a quiet hour.
Nuclei runs community-written templates. It sends real test requests, so treat it as an active scan. Run it on a staging copy, or on your live site only with a backup and during a quiet hour. Choosing higher-severity checks does not make it gentle, because high and critical templates often include exploit-style checks such as default logins and remote code execution probes.
nuclei -u https://yourdomain.com -severity high,critical
Proxies: ZAP and Burp Community
A proxy is a tool that sits between your browser and a website. It lets you see every request, pause it, change it and send it again. This is how testers check things like whether changing a number in a URL shows someone else's data.
Burp Community is the classic choice for this. Its Proxy and Repeater tools work well for learning. The automated scanner is only in the paid editions. ZAP also works as a proxy and is fully free, so it is a fine single tool to learn on.
Network tools: Nmap and Greenbone
Nmap checks which doors are open on a server. A basic check looks like this:
nmap -sV yourdomain.com
The -sV flag asks Nmap to guess the software behind each open port. You should expect ports 80 and 443 (web). Be suspicious of anything else that is reachable from the whole internet, such as a database port (3306 for MySQL) or remote desktop (3389).
On shared hosting, the server and IP address belong to your host and are shared with other customers. Check your host's policy before you scan it.
Greenbone Community Edition (built around OpenVAS) goes deeper by matching services against known vulnerabilities. It takes real setup time, so it suits teams with someone technical.
CMS tools: WPScan for WordPress
Many small-site break-ins do not need a clever attack. Outdated plugins are one of the most common ways WordPress sites get hacked. OWASP A06:2021, Vulnerable and Outdated Components explains why. WPScan checks your WordPress core, plugins and themes against a database of known vulnerabilities.
wpscan --url https://yourdomain.com --enumerate vp,vt --api-token YOUR_TOKEN
Here vp means vulnerable plugins and vt means vulnerable themes. A free API token from wpscan.com gives you vulnerability data, with a daily request limit. If this is a business site, the free WPScan licence may not cover you. Check the terms on wpscan.com before you use it.
Shopify, Wix and Squarespace owners have fewer options. You cannot test the platform itself, and you should not try. Check your apps, your theme and your store settings instead.
What is safe to run on your own site
The rule is simple: low-impact checks are usually safe on a site you own. Attack-style tests are not. A low-impact check asks your site or server ordinary questions, such as loading pages, reading headers or listing open ports. It still sends requests, so it shows up in your logs. An attack-style test sends crafted input to see what breaks, and it can slow down or damage a live site.
Generally safe on a site you own:
- ZAP baseline scan
curl -I https://yourdomain.comto view your response headers (or use the security headers tool)- testssl.sh against your domain
- Nmap basic port and version check (
nmap -sV), on a server you control - WPScan enumeration of plugins and themes
Run only on a staging copy, with a backup:
- ZAP active scan
- Nikto
- Nuclei (any severity)
- sqlmap (a tool that tests for SQL injection, where input tricks the database into running commands)
- Password guessing or brute-force tools
- Nuclei with intrusive templates
Follow these steps before any scan:
- Confirm you own the site or have written permission from the owner.
- Check your host's terms. Some hosts and platforms restrict scanning.
- Take a fresh backup.
- Start with the low-impact checks above.
- Scan during a quiet hour, and watch your site while the scan runs.
- Write down each finding with the tool, the URL and the date.
Scanning a site you do not own can be against the law in many countries, even when you mean no harm. Permission first, always.
What to do with the results
A list of findings is only useful if you act on it. Work through it in this order:
- Fix high-severity items and exposed services first. Examples are an open database or remote desktop port, or a plugin with a known flaw.
- Treat each scanner finding as unconfirmed until you verify it. Open the URL, read the tool's explanation and check that the problem is real, because false alarms are common.
- Rescan after every change to confirm the fix worked and nothing new broke.
What free tools miss
Free scanners are good at known, repeatable problems. They are weak at problems that depend on how your app is meant to work.
The top item on the OWASP Top 10 (2025) is broken access control. That means users can see or change things they should not, such as another customer's order. A scanner has no idea which customer should see which order, so it often misses this. A person testing by hand can check it.
Scanners also report false alarms and miss chained problems, where two small issues combine into a big one. Our guide on manual vs automated penetration testing covers the difference in more depth. For a method to follow yourself, the OWASP Web Security Testing Guide is the standard free reference.
When to hire a professional
Free tools are a good first pass. Move to a human when any of these are true:
- Your site holds customer accounts, orders or personal data.
- You take payments or handle logins.
- A client sent you a security questionnaire.
- Your scan results are long and you cannot tell what matters.
- You just shipped a big change, like a new checkout or login.
You can also start with no cost. The free website security check does a passive outside look at a domain you own. It is not manual testing and it has no report.
For manual testing, Bug Circuit's Essential plan is $49 one time for one month, with 1 website and 3 audits. A real security engineer tests the site by hand and sends a full written report with every issue, its severity, the evidence, the impact and fix steps. It is a small-site audit, not a multi-week enterprise pentest and not a compliance certificate. See plans and pricing, or read what a penetration test costs in our cost guide.
Key takeaways
- Start with ZAP (baseline scan), Nmap and, for WordPress, WPScan. ZAP and Nmap are free to use. WPScan's free plan is for non-commercial use, so check its terms for a business site.
- Only test sites you own or have written permission to test, and check your host's rules first.
- Keep to low-impact checks on live sites. Run active scans and attack tools, including Nikto and Nuclei, on a staging copy with a backup.
- Fix high-severity items first, verify each finding, and rescan after changes.
- Free scanners miss access-control and business-logic flaws, which a person can find. If you hold customer data or take payments, a manual audit is the honest next step.
A free scan tells you what a robot can see. A $49 human audit tells you what a person could do with it, and exactly how to fix it. Fixing is a separate service, quoted per issue, and you pay only if you agree to the price.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing