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 Enterprise plans.
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 CAs used by UptimeRobot. SSL certificates for custom status page domains are issued automatically — if your CAA policy doesn't include all of the following issuers, certificate issuance may fail or break in the future when a different CA is selected.
Add all four of the following CAA records to your domain:
0 issue "letsencrypt.org"
0 issue "pki.goog"
0 issue "ssl.com"
0 issue "sectigo.com"
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
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.
