# Active Recon ## Finding Documentation: ``` /api /swagger/index.html /openapi.json /api/swagger/v1/users/123 /api/swagger/v1 /api/swagger /docs /redoc ``` ## Nmap: ``` nmap -sC -sV [target address or network range] -oN nameofoutput ``` ``` nmap -p- [target address] -oA allportscan ``` ``` nmap -sV --script=http-enum -p 80,443,8000,8080 ``` ## Amass: ``` amass enum -active -d target-name.com |grep api ``` ``` amass intel -addr [target IP addresses] ``` ``` amass intel -d [target domain] –whois ``` ``` amass enum -passive -d [target domain] ``` ``` amass enum -active -d [target domain] ``` ``` amass enum -active -brute -w /usr/share/wordlists/API_superlist -d [target domain] -dir [directory name] ``` ## **Directory Brute-force with Gobuster** ``` gobuster dir -u target-name.com:8000 -w /home/hapihacker/api/wordlists/common_apis_160 -x 200,202,301 -b 302 ``` ## **Kiterunner** `kr scan HTTP://127.0.0.1 -w ~/api/wordlists/data/kiterunner/routes-large.kite` ``` kr brute -w ~/api/wordlists/data/automated/nameofwordlist.txt ``` ``` kr kb replay "GET 414 [ 183, 7, 8]://192.168.50.35:8888/api/privatisations/count 0cf6841b1e7ac8badc6e237ab300a90ca873d571" -w ~/api/wordlists/data/kiterunner/routes-large.kite ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://shahidulandshamim.gitbook.io/web-application/api-testing/reconnaissance/active-recon.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.