> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-tools/enumeration.md).

# Discovery and Enumeration Tools

Discovery and enumeration tools for DNS, service assessment, vulnerability scanning, exposed Git repositories, subdomains, web profiling, wireless sensing, and attack surface mapping.

Use this category to map target exposure: DNS records, subdomains, network services, vulnerability scan results, exposed Git repositories, wireless sensing research, and web technology signals.

## Tools and Resources

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-shield-halved" style="color:$primary;">:shield-halved:</i></h3></td><td><h4>Nessus</h4></td><td>Nessus vulnerability scanning notes for network, host, service, application, and operating system assessment.</td><td><a href="/hacking-tools/enumeration/nessus-scan-network-and-system.md">Nessus Network and System Scanning</a></td></tr><tr><td><h3><i class="fa-network-wired" style="color:$primary;">:network-wired:</i></h3></td><td><h4>DNS Enumeration</h4></td><td>DNS enumeration tooling notes for passive DNS discovery, subdomain enumeration, DNS records, zone transfer checks, dnsrecon, dnsenum, DNSDumpster, brute forcing, host discovery, and reconnaissance workflows.</td><td><a href="/hacking-tools/enumeration/dns-enumeration.md">DNS Enumeration</a></td></tr><tr><td><h3><i class="fa-network-wired" style="color:$primary;">:network-wired:</i></h3></td><td><h4>Network Service Assessment Tools</h4></td><td>Network service assessment tools for SMB, Kerberos, LDAP, SNMP, NFS, RPC, authentication testing, and Windows or Active Directory service enumeration.</td><td><a href="/hacking-tools/enumeration/network-service-assessment-tools.md">Network Service Assessment Tools</a></td></tr><tr><td><h3><i class="fa-wifi" style="color:$primary;">:wifi:</i></h3></td><td><h4>RuView WiFi Sensing</h4></td><td>RuView notes for WiFi CSI sensing, ESP32 setup, simulated demos, presence detection, movement research, and privacy-aware validation.</td><td><a href="/hacking-tools/enumeration/ruview-wifi-sensing.md">RuView WiFi Sensing</a></td></tr><tr><td><h3><i class="fa-code-branch" style="color:$primary;">:code-branch:</i></h3></td><td><h4>Git-Dumper</h4></td><td>Git-Dumper notes for recovering exposed .git directories and reviewing leaked repository history during web assessments.</td><td><a href="/hacking-tools/enumeration/git-dumper.md">Git-Dumper</a></td></tr></tbody></table>

### Workflow

1. Start with passive discovery and DNS context.
2. Validate exposed services and technology signals with targeted enumeration.
3. Run scanners only where scope and authorization are clear.
4. Confirm high-impact findings manually before reporting.
5. Keep raw output, versions, timestamps, and evidence paths.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/hacking-tools/enumeration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.