Custom domain on your status page

Custom domains let you serve each client's status page from a hostname they own. Instead of status.everguardly.com/acme, your client sees status.acmestudio.com — same data, no Everguardly branding in the URL.

Setup — step 1: attach the domain

In Dashboard → Status pages, click the + Domain button on the client row. Enter the hostname (lowercase, no protocol, no path — e.g. status.acmestudio.com) and submit. We register it with our Cloudflare-for-SaaS partner zone and return the verification CNAME record you need to publish at your DNS provider.

Setup — step 2: add the CNAME

Log into your DNS provider (Cloudflare, Route53, Namecheap, anywhere you can edit DNS) and add:

hostname:  <your-status-domain>     (e.g. status.acmestudio.com)
type:      CNAME
value:     <the target we show you>

Save. Within 60-90 seconds we'll detect the record and issue a free TLS certificate via Cloudflare's Universal SSL. The status panel flips from pending → active. Hit Refresh status to re-check on demand.

Apex domains (root domain, no subdomain)

DNS RFCs don't allow a CNAME at the apex — that means you cannot put a plain CNAME at acmestudio.com. If you want to serve the status page directly from the root domain (instead of a subdomain like status.acmestudio.com), you have two paths. We auto-detect apex input in the attach form and swap to apex-specific instructions.

Option 1 — CNAME flattening (recommended, Cloudflare Registrar only)

If your DNS is on Cloudflare, add the CNAME exactly like a subdomain — Cloudflare will resolve it at query time and answer with A records, RFC-compliant. Zero ongoing maintenance.

acmestudio.com     CNAME    <target we show after attach>

Option 2 — A records (works on any registrar)

On other registrars (Namecheap, GoDaddy, Route53, etc.), add A records pointing at our Cloudflare for SaaS Origin IPs. We show the exact IPs after you click Attach (they're stable; we publish them in the dashboard so you can re-look them up). You'll also need a one-time ownership-verification CNAME at _cf-custom-hostname.<your-apex> — Cloudflare auto-clears it once verified.

acmestudio.com                       A        <origin IP 1>
acmestudio.com                       A        <origin IP 2>
_cf-custom-hostname.acmestudio.com   CNAME    <verification target>

DNS propagation on Cloudflare settles in under a minute; elsewhere it can take several minutes (up to your TTL). Hit Refresh status once the records are live.

Slug URL still works

While the status is pending, the slug URL (status.everguardly.com/your-client) keeps working exactly as before. There's no downtime during the cutover. Once the custom domain goes active, both URLs serve the same page; you can keep the slug URL as a fallback or remove the custom domain at any time without affecting the slug.

How routing works

The middleware in front of our status page service does a single DB lookup keyed on the Host header your browser sends. If the host matches an active custom domain in our system, we rewrite the request to /status/<slug> internally. If it doesn't match, the host falls through to a normal 404. Disabled or private status pages are not reachable via custom domain even if DNS still resolves — security in depth.

Domain conflicts

A domain can only be claimed by one client across all of Everguardly. If you see "That domain is already in use on another status page," double-check you don't have another client claiming it, or contact support if you think the conflict is incorrect.

Removal

Hit Remove in the same Custom domain panel. We delete the CNAME from our partner zone and clear the row. The DNS record on your side still exists — you should delete it too, otherwise visitors who type that URL will get a generic "no such host" error from our partner.

Trade-offs

V1 uses Cloudflare for SaaS shared zone, which means TLS certs are issued under their roots (DigiCert/Let's Encrypt), not yours. For agency clients this is invisible. If you need EV / OV certificates or custom CA roots, V2 will support bring-your-own-cert.