A custom domain lets visitors open a status page at an address such as https://status.example.com/. Uptime Basics manages the HTTPS certificate and a dedicated edge distribution for the domain.
Your shared status.uptimebasics.com page remains available while the custom domain is active.
Requirements
Before starting:
- Enable the public status page.
- Complete ownership verification for the monitored website.
- Use the monitored domain or one of its subdomains.
- Have permission to change public DNS records.
For a monitor on www.example.com, a subdomain such as status.example.com is recommended. Enter only the hostname, without https://, a path, query string, or trailing slash.
Request the domain
- Open the monitor's Public Status Page settings.
- Open Custom domain.
- Turn on Request custom domain.
- Enter the custom hostname.
- Choose whether the custom page should remain out of search engines or allow indexing.
- Select Save custom domain request.
- Select Check / activate domain.
The first activation check requests a managed certificate. The page then displays a certificate-validation CNAME record.
Add the certificate-validation record
At your DNS provider, create the exact CNAME shown under Step 1 - Certificate validation:
- Type: CNAME
- Name: generated certificate-validation name
- Value: generated certificate-validation target
Some DNS providers append your domain automatically. Check the resulting full name so it does not contain the domain twice.
Keep this validation record after activation. The managed certificate can need it for renewal.
After the record is publicly visible, return to the editor and select Check / activate domain again. Certificate issuance can take time after DNS propagates.
Route the custom hostname
After the certificate is issued, Uptime Basics creates the dedicated edge distribution. When its target appears under Step 2 - Route status traffic, add the displayed CNAME:
- Type: CNAME
- Name: your custom hostname, such as
status.example.com - Value: the generated traffic target
Use a normal, unproxied DNS CNAME while activating the page. DNS proxying or CNAME flattening can prevent the verification check from seeing the required target.
Wait for DNS and edge deployment, then select Check / activate domain until the status becomes Active. The page is served from the custom hostname root, so visitors use https://status.example.com/ without the shared-page slug.
Disable or change the domain
Turn off Request custom domain and save when the custom address should stop working. The shared status page can remain enabled, while retirement of the dedicated certificate and distribution runs in the background.
Changing to another custom hostname also starts retirement of the previous domain resources and requires the new certificate and DNS process.