# Reconnaissance When attacking an Active Directory, or in fact any system, it is essential to gather useful information that will help define who, what, when and where. Here are some examples of what information to look for. * The location of the **domain controllers** (and other major AD services like KDC, DNS and so on). This can be achieved by [resolving standard names](broken://pages/byUqwWh4MzHCAqOzZsfW), by [scanning the network](/ad/recon/network/port-scanning.md) and with [standard LDAP queries](/ad/recon/network/ldap.md) * The **domain name**. It can be found with [standard LDAP queries](/ad/recon/network/ldap.md), recon through [MS-RPC named pipes](/ad/recon/network/ms-rpc.md), by combining [different recon techniques with enum4linux](/ad/recon/tools/enum4linux.md), by [inspecting multicast and broadcast name resolution queries](/ad/recon/tools/responder.md), ... * **Domain objects** and relations between them with [BloodHound](broken://pages/LC5HbzI57PEFYfKswdsj), with [MS-RPC named pipes](/ad/recon/network/ms-rpc.md) and with [enum4linux](/ad/recon/tools/enum4linux.md). --- # 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://red.infiltr8.io/ad/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.