> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scaling.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a Custom Domain

> Serve your public status page at your own subdomain — for example, status.example.com — over HTTPS.

By default, your public status page is served at `https://scaling.cloud/status/<slug>`. With a **custom domain**, you can serve the same page at a hostname under your control, such as `https://status.example.com`.

scaling.cloud handles TLS certificates automatically. You only need to add two DNS records: one TXT record to prove ownership, and one CNAME to route traffic. Occasionally we may also ask for an extra TXT record to confirm you control the hostname — the in-app settings panel will show it if so.

<Frame caption="The custom domain settings panel">
  <img src="https://mintcdn.com/scalingcloud/5-FlXcH6ySIwHzG0/images/placeholder.svg?fit=max&auto=format&n=5-FlXcH6ySIwHzG0&q=85&s=18ab9c45531fe92b117df1f9652cb357" alt="Custom domain settings" width="1200" height="675" data-path="images/placeholder.svg" />
</Frame>

## Prerequisites

* A published [status page](/guides/publish-status-page).
* A subdomain you control (e.g., `status.example.com`). **Apex domains are not supported** — you must use a subdomain.
* Access to your DNS provider to add `TXT` and `CNAME` records.
* The **Admin** role in your scaling.cloud organization.

<Steps>
  <Step title="Open custom domain settings">
    Go to **Settings → Status Page** and scroll to the **Custom domain** section.
  </Step>

  <Step title="Add your hostname">
    Click **Add domain** and enter the subdomain you want to use (e.g., `status.example.com`). Click **Save**.

    scaling.cloud validates the hostname and creates a verification record. The domain state is now `pending_verification`.
  </Step>

  <Step title="Add the TXT verification record">
    scaling.cloud shows you a TXT record to add to your DNS:

    ```
    Name:  _scaling-verification.status.example.com
    Type:  TXT
    Value: scaling-verify=<your-token>
    ```

    Add it at your DNS provider exactly as shown. Most providers propagate within a few minutes; some take up to an hour.

    scaling.cloud re-checks the record automatically every few minutes. When the value matches, the domain transitions to `verified`.
  </Step>

  <Step title="Add the CNAME routing record">
    Once ownership is confirmed, the settings panel shows you a CNAME to add at your DNS provider. The record name is your hostname (e.g. `status.example.com`) and the value is the hostname shown in the panel — copy it exactly as displayed.

    Add the CNAME at your DNS provider. TLS is provisioned for you automatically; you don't need to manage certificates.
  </Step>

  <Step title="Add an extra TXT record if requested">
    If your hostname is already attached to a different account on our routing layer, the settings panel will show you an additional TXT record to add. Copy the name and value exactly as displayed and add it alongside the records above. This proves you control the hostname so it can be moved to your scaling.cloud org.
  </Step>

  <Step title="Wait for the domain to go live">
    scaling.cloud polls the routing layer every couple of minutes. Once the CNAME (and the optional TXT) are in place, the domain state moves to `active` and your status page is reachable at `https://status.example.com` over HTTPS.
  </Step>
</Steps>

## States

| State                  | Meaning                                                                                             |
| ---------------------- | --------------------------------------------------------------------------------------------------- |
| `pending_verification` | Waiting for the TXT record to appear with the expected token.                                       |
| `verified`             | Ownership confirmed; finalizing routing setup.                                                      |
| `hosting_pending`      | Waiting on the routing CNAME (and optional verification TXT) to be set.                             |
| `active`               | Live. Traffic to your hostname is served over HTTPS.                                                |
| `misconfigured`        | The routing layer could not verify your hostname after multiple attempts. Recheck your DNS records. |

## Removing a custom domain

To stop serving your status page at the custom hostname:

1. Go to **Settings → Status Page → Custom domain**.
2. Click **Remove**.
3. scaling.cloud detaches the hostname. Your page remains reachable at `https://scaling.cloud/status/<slug>`.

After removal, you can also delete the TXT and CNAME records at your DNS provider.

## Limitations

* **One custom domain per organization.** Multi-domain support is on the roadmap.
* **Subdomains only.** Apex domains (e.g., `example.com`) are not supported.
* **No bring-your-own certificate.** TLS is always managed for you.