# Web Enumeration ## Vectors Firstly interact with the website and ask yourself: * What language is the app written in? * what server software is the application running on? * What does the application do? * What is the technology stack? * etc. The browser's dev tools can help \[also, the [Wappalyzer](https://www.wappalyzer.com/) extension can help recognize technologies]. Look for a sitemap like **robots.txt** and **sitemap.xml**. Some sites ship with remote administration web applications, for example /manager/html \[Tomcat] and /phpmyadmin \[MySQL]. **Try to log in with default creds**. ## Tools ### Nikto A good scanning tool for catching low hanging fruit. **Very noisy!** ### **Gobuster** Directory \[and DNS] busting. Rumored to be stabler and faster than **dirbuster** and **dirb**. Usage example: ``` gobuster dir -u -w -c -x ``` --- # 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://nickbhe.gitbook.io/shikata-ga-nai-1/gaining-access/web/web-enumeration.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.