🩸
Pentesting Checklist
  • πŸ‘€General Checklist
    • πŸ‘οΈRecon & Scanning
      • Nmap Scan
    • 🌑️Services
      • SSH
      • FTP
      • Samba
      • Git
      • SNMP
    • βš™οΈReverse Engineering
      • General
      • Android apks
      • Windows Exe or .net binaries
  • 🐞Web Application Checklist
    • 🧠Web App Attack Techniques
      • Password Smuggling Attack
    • 😍Fuzzing with ffuf
    • πŸ’„Directory Fuzzing
      • Using the tools
      • Wordlists to use
    • πŸ‘ΎSubdomain Fuzzing
      • Normal fuzzing
      • Finding through DNS
    • 🎯LFI/RCE
      • LFI
        • What to do once obtained
      • RCE
      • Misc
  • β˜•Linux Checklist
    • Page 2
  • πŸͺŸWindows Checklist
    • πŸ’€Windows Connection Methods
  • πŸ–‡οΈTips & Tricks
    • Transferring Files
      • 🐧Linux
      • πŸ“ΈWindows
    • Pivoting / Lateral Movement Techniques
      • proxychains
      • chisel
      • sshuttle
      • ligolo-ng
    • 🧩Fuzzing
    • πŸ™ƒCredential Brute-Forcing
  • πŸ’Other useful resources:
    • Page 7
Powered by GitBook
On this page
  1. General Checklist
  2. Recon & Scanning

Nmap Scan

Initial system scan with nmap

  1. sudo nmap -p- --min-rate 10000 -oN nmap/minrate $IP

    • Quick scan for all ports (might miss some ports)

    • To get comma separated list of only ports to use in next commands

      • cat nmap/minrate | grep open | awk -F/ '{print $1}' ORS=','; echo

  2. sudo nmap -p -sC -sV -oN nmap/scriptscan $IP

    • Take all the ports from first scan and run this scan on them

  3. sudo nmap -p- -oN nmap/norate $IP

    • Another long scan just to make sure no ports were missed

    • If this found more ports, rerun the scriptscan

  4. Maybe run a -Pn scan to ping ips that won’t respond

  5. Then sudo nmap -sU -oN nmap/udp $IP in the background since it takes long

    • Nmap UDP scan

Nmap scans on an entire subnet is also possible by adding the /subnet after the ip (192.168.0.0/24)

PreviousRecon & ScanningNextServices

Last updated 2 years ago

πŸ‘€
πŸ‘οΈ