Kportscan 3.0 ✰

Scenario: You want to confirm that port 443 (HTTPS) is reachable from an internal segment to a DMZ server.

For power users, KPortScan 3.0 includes a built-in Lua-based scripting engine. You can write simple scripts that:

Create a file nightly_scan.lua:

-- KPortScan 3.0 script
target = "192.168.1.0/24"
ports = "21,22,23,80,443,3389,8080"
scan_type = "syn"
output_file = "C:\\scan_results\\" .. os.date("%Y-%m-%d") .. ".csv"
kpscan.scan(target, ports, scan_type)
kpscan.export(output_file, "csv")
kpscan.email("admin@company.com", "Nightly scan complete", output_file)

Run via command line: KPortScan3.exe --script nightly_scan.lua kportscan 3.0

Schedule this using Windows Task Scheduler for daily 3 AM scans.

We listened to the community. We analyzed GitHub issues, read the tweets, and looked at our own pain points. Here is how we addressed them.

If you want, I can:

| Scan type | Snort | Suricata | Zeek | |-----------|-------|----------|------| | Nmap -sS (default) | 94% | 91% | 88% | | Masscan (rate=5k) | 98% | 95% | 92% | | KPortScan 3.0 (high-speed) | 85% | 79% | 74% | | KPortScan 3.0 (stealth + decoy) | 12% | 9% | 14% | | KPortScan 3.0 (morphing + ML delay) | 4% | 3% | 6% |

KPortScan 3.0 requires no external dependencies (no WinPcap or Npcap needed for basic scans, but SYN scans require the included KPCap driver).

Step-by-step:

First-run note: On Windows 11, you may need to allow “Raw Socket Access” in Windows Security > App & Browser Control > Exploit Protection > Network Security Settings.

Version 3.0 sets the foundation for the future of the project. We are already looking at features for 3.1, including: