> For the complete documentation index, see [llms.txt](https://vulp3cula.gitbook.io/hackers-grimoire/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vulp3cula.gitbook.io/hackers-grimoire/recon.md).

# Reconnaissance

## Passive information gathering (OSINT)

Passive information gathering is about collecting information about a target from public sources, such as search engines, social media and organizational websites. This work is usually performed before the penetration test, or is part of the scoping exercise. The reason it is considered passive is that the activities aren't intrusive or highly detectable like scanning servers or other assets.

## Active information gathering

Active information gathering is the processes of gathering information about a system or network to better understand the attack surface (opportunities for exploitation) before a penetration test. It's usually more prone to detection because it involves port scanning, service enumeration and OS fingerprinting. Enumeration should be as comprehensive as possible, for example don't forget to scan TCP, UDP and higher port ranges. Many services can reside on higher ports, including common ones like **ssh**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vulp3cula.gitbook.io/hackers-grimoire/recon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.