> For the complete documentation index, see [llms.txt](https://docs.bfore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bfore.ai/docs/console/takedowns-list.md).

# Takedowns list

The **Takedowns** page tracks the status of your takedown requests for malicious infrastructures targeting your assets. It shows takedowns of every type together: attacks identified by PreCrime, attacks reported by your team, and social media takedowns.

## Takedown cards

Each takedown shows:

* The takedown URL, with a copy button.
* **Protected asset** - the asset the attack targets.
* **Requested by** - who requested the takedown.
* A status chip (see [Takedown statuses](/docs/console/takedowns-list/takedown-statuses.md)). For cancelled or rejected takedowns, click the chip to see the reason.
* **Created** date, or for completed takedowns the **Process Time** and completion date.
* **Cost saved** - the estimated attack cost avoided, shown once the takedown is actively worked or completed.
* **Process phase** - the detailed stage the takedown is in. Possible values are: Under review, In progress, Completed, Cancelled, Rejected.
* **Details** - opens the related [attack detail page](/docs/console/disrupted-attacks/attack-details.md) in a new tab (not available for social media takedowns or reported attacks still under review).
* **Cancel** - Admins only, on takedowns that have not reached a final state.

## Filtering and searching

* **Search takedown URL** - type and press Enter. This is a partial match, not an exact match. When a search is active, results include matches from all time regardless of the date range selected - see [Search overrides the date range on some pages](/docs/console/filters-search-and-exports.md#search-overrides-the-date-range-on-some-pages).
* **Date range** - presets from Today up to Year to date, or a custom range. Defaults to the last 30 days. Disabled while a search is active.
* **Protected domain** - a searchable multi-select of your company's monitored domains.
* **Status** - Under review, In progress, Completed, Cancelled, Rejected.
* **Type** - Identified attacks (found by PreCrime), User reported attacks, Social media.
* **Order by** - newest to oldest (default) or oldest to newest.
* **Page size** - 20, 50, or 100 items per page.

Filters are reflected in the page URL, so you can bookmark or share a filtered view.

## Adding a takedown request

Admin users see an **Add takedown** button at the top of the page. Use this to request a takedown for infrastructure PreCrime has not identified itself (see [Requesting a takedown](/docs/console/takedowns-list/requesting-a-takedown.md)). This button is not available to Read only users.

## Exporting

The **CSV** button exports the filtered list as `takedowns.csv`, including the creation date, attack URL, asset name, takedown status, takedown type, last updated timestamp, and requester.


---

# 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://docs.bfore.ai/docs/console/takedowns-list.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.