> 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/requesting-a-takedown.md).
# Requesting a takedown
Admins can request a takedown for malicious infrastructure your team has found, even if PreCrime has not identified it as an attack - giving you a direct way to act immediately on your own findings. Click **Request takedown** on the [Takedowns page](/docs/console/takedowns-list.md).
The dialog has three tabs.
## Domain takedown
Request to take down attacks targeting your brand. Fields:
* **Malicious URL** (required) - the attacking URL.
* **Target asset** (required) - which of your protected assets is being attacked. A dropdown selection of your active assets is available.
* **Comments** (required, at least 10 characters) - details about the takedown request that will help PreCrime process your request.
## Social Media takedown
Request to take down fraudulent social media accounts or posts targeting your brand. Fields:
* **Type of attack** (required)
* **Platform** (required) - choose from a list of available platforms. If the platform is not on the list, choose **Other**.
* **Malicious URL** (required) - the malicious URL you want to take down.
* **Target asset** (required) - the asset under attack.
* **Comments** (required, at least 10 characters) - provide as much detail about the threat as possible.
## WhatsApp takedown (Beta)
Request to take down WhatsApp scams or impersonation targeting your brand. This tab contains an embedded form. Your account email address is filled in automatically and cannot be changed.
Fields:
* **Malicious Phone number** (required) - the WhatsApp number you'd like PreCrime to take down.
* **Ticket description** (required) - provide as much detail about the threat as possible.
* **File upload** (optional) - attach supporting evidence such as screenshots of conversations, a WhatsApp profile, or anything else that can help with the takedown.
{% hint style="info" %}
Attach screenshots showing the profile picture and the malicious solicitation itself, for example a click link or chat prompt. Since WhatsApp requests are handled manually, this speeds up processing.
{% endhint %}
This feature is request-only while in beta - once submitted, you cannot yet see or manage the status of WhatsApp takedowns on the platform (they will not appear in your takedowns list).
## After you submit
After a successful submission, the dialog closes and you will see one of two confirmation messages:
* **"Thank you for submitting your takedown request. Our team is carefully reviewing the details."** - your request has been received and is now under review.
* **"This attack was already identified by our system. A takedown has been initiated anyway."** - PreCrime had already detected this threat independently. A takedown has still been created on your behalf.
In both cases, the takedown follows the normal [takedown lifecycle](/docs/console/takedowns-list/takedown-statuses.md) from this point.
If a takedown for the same URL already exists, the platform tells you and closes the dialog - no duplicate is created. You can find the existing takedown in your [takedowns list](/docs/console/takedowns-list.md).
If the **Malicious URL** you entered is not a valid URL, an error message appears directly on that field. Correct the URL and resubmit.
Switching tabs clears any field-level error messages, but does not discard anything you have already typed.
Takedowns on attacks PreCrime has already identified do not need to be submitted via this form - use the **Start takedown** button on the attack itself (see [Managing takedowns](/docs/console/takedowns-list/managing-takedowns.md)).
---
# 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/requesting-a-takedown.md?ask=&goal=
```
`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.
