Summary
Using a custom domain (e.g. status.yourcompany.com) instead of the default stats.uptimerobot.com URL gives your status page a professional, branded look. This article walks you through the setup.
Requirements
Custom domains are available on Solo, Team, and Scale plans.
Your custom domain must be a subdomain (e.g. status.yourcompany.com). Apex/root domains (e.g. yourcompany.com by itself, with no subdomain) are not supported — domain verification only checks for a CNAME record, and most DNS providers won’t let you create a CNAME at the domain root. If you want visitors to reach your status page from the root domain, point a subdomain like status.yourcompany.com at UptimeRobot and redirect your root domain to it at your DNS or hosting provider.
Step 1: Add your custom domain in UptimeRobot
Go to Status Pages in your dashboard and open the status page you want to configure.
Under Settings, find the Custom Domain field.
Enter the subdomain you want to use (e.g.
status.yourcompany.com).Save your changes.
Step 2: Create a CNAME record with your DNS provider
In your DNS provider’s dashboard, create a CNAME record pointing your chosen subdomain to:
stats.uptimerobot.com
Example:
Type | Name | Value |
CNAME | status | stats.uptimerobot.com |
DNS propagation can take up to 24–48 hours, though it’s typically much faster.
Step 3: DNS CAA records (if applicable)
If your domain uses CAA (Certification Authority Authorization) records to restrict which certificate authorities can issue SSL certificates for your domain, you need to explicitly permit the CA UptimeRobot uses. SSL certificates for custom status page domains are issued automatically via Let’s Encrypt — if your CAA policy doesn’t permit letsencrypt.org, certificate issuance will fail.
Add the following CAA record to your domain:
0 issue "letsencrypt.org"
If your domain has no CAA records at all, no action is needed.
Cloudflare users
If your domain is behind Cloudflare, make sure the CNAME record for your status page subdomain has the proxy disabled (grey cloud, DNS-only mode). Using Cloudflare’s proxy or Flexible SSL will cause redirect or certificate errors.
Troubleshooting
Domain returns a 404, but it was working before and your DNS hasn’t changed: Check this before re-verifying DNS. Check that your account is still on a plan that includes Custom Domain (Solo and up) — a downgrade, an expired trial, or a failed payment immediately blocks the whole page on your custom domain, even though your DNS and SSL certificate are still configured correctly. Restoring the plan resolves the 404 right away.
ERR_SSL_PROTOCOL_ERROR / SSL handshake error: Most commonly caused by a missing CAA record (see Step 3) or Cloudflare proxy being enabled.
“No such site” error: The CNAME hasn’t propagated yet, or the custom domain in your UptimeRobot settings doesn’t exactly match the subdomain you configured.
Certificate takes time to appear: SSL certificates are issued automatically after the CNAME is detected. Allow a few minutes after DNS propagates.