> 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/domain-takeover-scan.md).

# Domain takeover scan

The **domain takeover scan** checks whether your subdomains (e.g. pointing to CNAMEs like `*.github.io`, `*.s3.amazonaws.com`) are vulnerable to **subdomain takeover**. If the target service is not claimed, an attacker could claim it and serve content on your subdomain.

## What it does

* For each selected subdomain, resolves CNAMEs (or similar) and checks if the target service is unclaimed or misconfigured.
* Results indicate which subdomains are likely vulnerable to takeover, with service type and evidence.
* You can then claim the service or remove the DNS record to prevent abuse.

## Options

* **Subdomain selection:** Choose which subdomains to scan (or all).

## Availability

* **All plans** (Free, Basic, Premium, Enterprise).
* 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/domain-takeover-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.