> For the complete documentation index, see [llms.txt](https://bugrecon.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugrecon.gitbook.io/docs/features-list/scopes-overview/vulnerability-scan.md).

# Vulnerability scan

The **vulnerability scan** runs **vulnerability checks** on your subdomains. It helps you find known CVEs, misconfigurations, and security issues in a structured way.

## What it does

* For each selected subdomain, runs a vulnerability scanner
* Choose the category of test you want to test.
* Results include severity and description. They are stored per subdomain and shown in the scan detail; you can filter by severity or template.

## Options

* **Template selection:** By category or "ALL" (e.g. cve, misconfiguration, exposure). Custom templates from Settings may be selectable.
* **Subdomain selection:** Choose which subdomains to scan (or all).

## Availability

* **Basic**, **Premium** and **Enterprise** only. **Free** users do not have access.
* Uses your **scan quota** when you run it.


---

# 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://bugrecon.gitbook.io/docs/features-list/scopes-overview/vulnerability-scan.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.