> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/organization-and-account-settings/domains/delete-custom-domain.md).
# Delete custom domain
{% hint style="success" %}
**Access Type:** Domains - Editor
{% endhint %}
In this article, we will cover how to delete a custom domain from your organization's account via the Didomi console. The steps involved in deleting a custom domain differ slightly depending on whether the [usage for the custom domain](/organization-and-account-settings/domains/domain-usage.md) is for serving the Didomi SDK or serving a hosted page.
{% hint style="info" %}
Only custom domains with a **Ready**, **Draft,** or **Failed** status can be deleted.
{% endhint %}
Click **My organization** in the header and select **Organization settings** from the drop-down menu.
Ensure the **Domains** tab is selected and navigate to a custom domain on the subsequent list with a **Ready**, **Draft**, or **Failed** status.
Click the **Delete** icon inline with the custom domain.
Usage
Deletion requirements
Serve a hosted page
Detach the custom domain from the widget before proceeding with the deletion.
Serve the Didomi SDK
No deletion requirements.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didomi.io/organization-and-account-settings/domains/delete-custom-domain.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
