Branding & custom domains
Add your logo and accent colour, remove SutramX branding with white-label, and serve your status page from your own domain with automatic HTTPS.
Make your status page look like part of your product: add your logo and brand colour, hide the SutramX footer, and serve the page from a hostname you own, such as status.example.com. All of this is set in the page editor: open Status pages in the sidebar, then click a page.
Branding#
The Branding section of the editor has:
| Field | What it does | Default / limits |
|---|---|---|
| Logo URL | An image shown next to the page title, about 48px tall. | Optional. Must be an https:// URL, up to 2,048 characters |
| Accent colour | Colour of the band at the top of the page. Pick it with the colour picker or type a hex value. | #0d9488 (teal). Must be a six-digit hex value such as #1d4ed8 |
Click Save changes. Logo and accent colour are available on every plan.
The status colours (green for operational, amber for degraded and maintenance, red for outages) never change, so visitors can always read the page at a glance.
White-label#
On Pro, the White-label part of Branding lets you remove SutramX branding:
| Field | What it does |
|---|---|
| Hide the "Monitored by SutramX" footer | Removes the footer link, and removes "· SutramX" from the browser tab title. |
| Favicon URL | Your own favicon for the page, as an https:// URL. |
If your workspace moves to a plan without white-label, the "Monitored by SutramX" footer comes back and your custom favicon is no longer used. See Plans & limits.
Custom domains#
Serve your status page from your own hostname, for example https://status.example.com/. Custom domains are available on Growth and Pro, and only the workspace owner can add, verify or remove one. Each page can have one custom domain.
The page stays available at its https://app.sutramx.com/status/<slug> address as well.
Step 1: Choose a hostname#
Use a subdomain you control, such as status.example.com. Verification checks for a CNAME record on the hostname, so a root domain (example.com) usually can't be used: most DNS providers don't allow a CNAME there, and "flattened" or ALIAS records don't pass the check.
You can't use a sutramx.com hostname, and a hostname that is already verified for another status page can't be added again.
Step 2: Add the domain#
- Open the page and go to Custom domain.
- Enter the hostname in Domain, without
https://or a path. - Click Set domain.
The domain is saved as Pending verification, and the panel shows the two DNS records to add.
Step 3: Add the DNS records#
At your DNS provider, add both records exactly as shown in the panel. Use the copy buttons to avoid typos.
| Type | Name | Value |
|---|---|---|
| TXT | _sutramx-verify.status.example.com | The verification token shown in the panel, which starts with sutramx-verify- |
| CNAME | status.example.com | cname.sutramx.com (the target shown in the panel) |
The TXT record proves you control the domain. The CNAME sends your visitors' traffic to SutramX. Both must be in place for verification to pass.
Some DNS providers add your domain to the name automatically. If yours does, enter only the part before it, for example _sutramx-verify.status for the TXT record and status for the CNAME.
In a BIND-style zone file for example.com, the records look like this:
_sutramx-verify.status IN TXT "sutramx-verify-<token from the panel>"
status IN CNAME cname.sutramx.com.Step 4: Verify#
- Wait for the records to propagate. This usually takes a few minutes, occasionally up to an hour.
- Click Verify.
When both records are correct, the domain shows Verified and the editor's public URL changes to your domain. If verification fails, the panel shows why:
| Problem | What it means | What to do |
|---|---|---|
| Could not find the verification TXT record | No TXT record at _sutramx-verify.<your domain> yet. | Check the record name, then wait a few minutes and verify again. |
| Verification TXT record found but did not match | A TXT record exists but its value is different. | Copy the value exactly, without extra quotes or spaces. |
| The CNAME does not point to the target | The TXT record is correct, but the hostname's CNAME is missing or points somewhere else. | Point the CNAME at the target shown in the panel (cname.sutramx.com). On Cloudflare, switch it to DNS only. |
| DNS lookup failed or timed out | A temporary DNS problem. | Try again in a few minutes. |
The panel also shows when the domain was last checked.
Step 5: HTTPS#
You don't need to upload a certificate. After the domain is verified, SutramX issues an HTTPS certificate automatically on the first HTTPS visit to the domain. Open https://status.example.com/ once in your browser to trigger it; the first visit can take a few seconds longer.
To see the certificate's state, click Check SSL under HTTPS certificate:
| Result | Meaning |
|---|---|
| Active | A trusted certificate is being served. The issuer and expiry date are shown. Certificates renew automatically. |
| No certificate served yet / Certificate not trusted yet | Issuance hasn't finished. Open the domain in a browser and check again shortly. |
| Could not connect / Timed out connecting to the domain on port 443 | The hostname doesn't reach SutramX. Check that the CNAME is still in place and not proxied. |
Change or remove the domain#
To use a different hostname, click Remove domain and add the new one. Removing a domain takes effect immediately: visitors using it can no longer reach the page, but the page stays available at its /status/ URL. You can remove a domain on any plan.
If you change your DNS later, keep the CNAME in place. The TXT record is only needed for verification, but leaving it does no harm.
If your plan changes#
If your workspace moves to a plan without custom domains, the domain stays configured but stops serving your page, and it can't be re-verified. Visitors can still reach the page at its /status/ URL. Upgrade again or remove the domain. See Upgrade, downgrade & cancel.
Custom domains and private pages#
On a custom domain, visitor sign-in for private pages happens on your domain too: the OIDC redirect URI and SAML ACS URL use it. If you add, change or remove the domain after setting up SSO, update the URLs registered with your identity provider. See Private pages & SSO.
Common questions#
Can I use the same domain for two pages? No. Each hostname can serve one status page. Use a different subdomain for each page, for example status.example.com and status.example.org.
Can the page live at a path, like example.com/status? No. A custom domain serves the page at the root of the hostname.
Does the badge or feed use my domain? No. The badge and feed URLs stay on https://api.sutramx.com. See Status pages overview.
Why does my domain still show Pending verification? You haven't clicked Verify since adding the records, or a check failed. Click Verify again; the panel shows the reason if it fails.
Related
- Status pages overview
- Private pages & SSO
- Subscribers & updates
- Plans & limits
- Features: Public Status Pages
- Guides: Status Page Best Practices and Incident Response Basics
- Free tools: Incident Message Generator
- Use cases: Monitoring for SaaS Platforms
- More from SutramX: Status Page Features
Last updated . Something unclear or missing on this page? Tell us at support@sutramx.com.