> ## Documentation Index
> Fetch the complete documentation index at: https://pulse-41cf5b0d.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Use a Custom Domain for Your Status Page

> Point status.yourcompany.com to your PulseGuard status page with a simple CNAME record. SSL is provisioned automatically.

Serving your status page from your own domain — such as `status.yourcompany.com` — keeps your brand consistent and builds user trust. When an incident occurs, customers who already recognise your domain are more likely to check the status page than navigate to an unfamiliar third-party URL. PulseGuard handles SSL certificate provisioning automatically, so there is nothing to configure on the TLS side beyond the DNS record.

## Set up a custom domain

<Steps>
  <Step title="Open your status page settings">
    Go to **Dashboard → Pages**, select the status page you want to configure, then click the **Settings** tab and choose **Custom Domain** from the left-hand menu.
  </Step>

  <Step title="Enter your domain">
    Type the full subdomain you want to use — for example, `status.acme.com` — into the **Custom Domain** field and click **Save**.
  </Step>

  <Step title="Add a CNAME record in your DNS provider">
    Log in to your DNS provider (Cloudflare, Route 53, Namecheap, etc.) and add the following record:

    ```
    Type:  CNAME
    Host:  status
    Value: cname.vercel-dns.com
    TTL:   3600
    ```

    The **Host** field is the subdomain prefix — use `status` if your domain is `acme.com` and you want `status.acme.com`. Some DNS providers label this field **Name** or **Subdomain**.
  </Step>

  <Step title="Wait for DNS propagation">
    DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. In practice, most providers apply changes within 5–15 minutes. You can verify propagation using a tool like [dnschecker.org](https://dnschecker.org).
  </Step>

  <Step title="SSL certificate is provisioned automatically">
    Once PulseGuard detects that the CNAME is resolving correctly, it automatically requests and provisions a TLS certificate for your domain. Your status page is then available over HTTPS with no manual steps required.
  </Step>
</Steps>

<Note>
  SSL certificates are provisioned and renewed automatically once PulseGuard detects the CNAME is resolving correctly. You never need to rotate certificates manually.
</Note>

<Warning>
  DNS propagation can take up to 48 hours in rare cases, depending on your DNS provider and your visitors' local resolvers. During this window, some users may still see the default `app.pulseguard.io` URL. Do not remove the old URL from any public communications until you have confirmed the custom domain is resolving for all regions.
</Warning>

## Verify your domain

After saving the custom domain, the settings page shows a **verification status** indicator with one of the following states:

| Status          | Meaning                                                                    |
| --------------- | -------------------------------------------------------------------------- |
| **Pending**     | PulseGuard has not yet detected the CNAME record.                          |
| **Propagating** | The CNAME is detected but DNS has not fully propagated.                    |
| **Active**      | The domain is resolving correctly and SSL is provisioned.                  |
| **Error**       | The CNAME is missing or points to the wrong target. Check your DNS record. |

## Password protection

You can restrict access to your status page — including the custom domain — by enabling password protection. Go to **Pages → your page → Settings → Visibility** and toggle **Password Protection** on, then set a password.

Visitors who navigate to your custom domain will be prompted to enter the password before the page loads. This is useful for:

* **Internal status pages** shared only with your engineering team or on-call staff.
* **Partner-facing pages** where you want to limit visibility to specific customers.

<Info>
  Password protection and custom domains work independently. You can use a custom domain on a public page, a password-protected page, or both simultaneously.
</Info>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I use an apex domain (e.g., acme.com) instead of a subdomain?">
    Apex domains (also called root or naked domains) cannot use CNAME records according to the DNS specification. Use a subdomain such as `status.acme.com` instead. Some DNS providers support CNAME flattening or ALIAS records that allow apex-like behaviour — check your provider's documentation for details.
  </Accordion>

  <Accordion title="Can I use multiple custom domains for one status page?">
    Each status page supports one active custom domain at a time. If you need separate domains for different audiences, create a separate status page for each one.
  </Accordion>

  <Accordion title="What happens if I remove my custom domain?">
    Removing the custom domain from your settings causes PulseGuard to stop routing traffic for that domain. Your status page immediately becomes accessible again via the default `app.pulseguard.io/status-page/<slug>` URL. The SSL certificate for your custom domain is revoked automatically.
  </Accordion>

  <Accordion title="Do I need to add a CAA DNS record for SSL?">
    If your DNS zone has CAA records that restrict which certificate authorities can issue certificates for your domain, you may need to add a permissive entry for the CA used by PulseGuard's hosting provider. If you have no existing CAA records, no action is needed. Contact support if you encounter certificate provisioning errors after the CNAME is in place.
  </Accordion>
</AccordionGroup>