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

# Custom domain

> Use your own domain (e.g. status.yourcompany.com) for your status page.

Instead of `status.obsy.ai/your-org`, you can serve your status page from a custom hostname like `status.yourcompany.com`. Custom domains use Cloudflare for SSL certificate provisioning.

***

## Prerequisites

* Your domain's DNS is managed by Cloudflare (or you can add a CNAME at your DNS provider pointing to Cloudflare)
* You have access to add DNS records at your domain registrar or Cloudflare dashboard

***

## Setup

### Step 1 — Configure in Obsy

1. Go to **Status Page → Settings → Custom domain**.
2. Enter your hostname (e.g. `status.yourcompany.com`).
3. Click **Save**.

Obsy creates a Cloudflare Custom Hostname record and begins SSL certificate provisioning.

### Step 2 — Add a CNAME record

At your DNS provider, create a CNAME record:

| Type  | Name     | Value            |
| ----- | -------- | ---------------- |
| CNAME | `status` | `status.obsy.ai` |

If your DNS provider requires a trailing dot: `status.obsy.ai.`

### Step 3 — Wait for SSL provisioning

SSL certificate provisioning typically takes 5–15 minutes. The status in Obsy's Status Page settings will show:

* **Pending** — certificate is being issued
* **Active** — domain is live and HTTPS is working
* **Error** — check that the CNAME record is correct and propagated

Once the status shows **Active**, your custom domain is live.

***

## Verifying

Visit `https://status.yourcompany.com` in a browser. You should see your Obsy status page with a valid SSL certificate.

***

## Removing a custom domain

Go to **Status Page → Settings → Custom domain** and click **Remove**. Your status page returns to the default `status.obsy.ai/{slug}` URL. The Cloudflare Custom Hostname record is deleted automatically.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Status shows 'Pending' for more than 30 minutes">
    Verify the CNAME record is correctly set and has propagated. Use `dig status.yourcompany.com CNAME` to check. If the record is correct and it's been over an hour, contact [support@obsy.ai](mailto:support@obsy.ai).
  </Accordion>

  <Accordion title="SSL certificate error in browser">
    This usually means the CNAME hasn't propagated yet. Wait 15–30 minutes and try again. Some DNS providers take longer to propagate changes.
  </Accordion>

  <Accordion title="Status shows 'Active' but the page doesn't load">
    Ensure there's no conflicting DNS record (e.g. an A record for `status` that overrides the CNAME). Check for proxied vs DNS-only records in Cloudflare.
  </Accordion>
</AccordionGroup>