> For the complete documentation index, see [llms.txt](https://docs.simptel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simptel.com/tf-platform/administration/organizations/projects/tenants/domains/remove-custom-domain.md).

# Remove custom domain

This article provides instructions for removing a custom domain in the TF Platform.

#### Removing a Custom Domain

**Step 1: Remove the Domain**

* Select the custom domain you wish to remove.
* Click **Delete**. A confirmation dialog will appear.

**Step 2: Confirm Deletion**

* Review the warning, fill in the confirmation prompt, then click **Delete** again to confirm and finalize the removal.

**Step 3: Update DNS Records**

* Access your DNS provider's console after the domain is removed from the platform.
* Remove or unpoint the CNAME record linked to the deleted domain.

{% hint style="warning" %}
Removing a custom domain will disrupt all associated services and features, rendering them inaccessible. Ensure you are prepared for this impact before proceeding with deletion.
{% endhint %}


---

# 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.simptel.com/tf-platform/administration/organizations/projects/tenants/domains/remove-custom-domain.md?ask=<question>&goal=<user_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.