From 7d87e368258fbb97aa3996706b459ff291386a85 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Fri, 6 Nov 2026 21:19:43 -0500 Subject: [PATCH 1/5] docs: describe status page custom domain certificates and renewal New custom domains validate their certificate over HTTP with only the CNAME record, so the TXT step is now conditional. Adds a section on automatic renewal, CAA records, the certificate messages shown in the status page settings, and the renewal emails. Co-Authored-By: Claude Opus 5.5 --- communicate/status-pages/custom-domain.mdx | 33 ++++++++++++++++------ 1 file changed, 25 insertions(+), 8 deletions(-) diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index d8a15f21b..882948da7 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -5,7 +5,7 @@ sidebarTitle: "Custom Domain" canonical: 'https://www.checklyhq.com/docs/communicate/status-pages/custom-domain/' --- -You can host your status page on your own domain. To set it up, add the domain in Checkly and create the required DNS records with your DNS provider. +You can host your status page on your own domain. To set it up, add the domain in Checkly and create the required DNS records with your DNS provider. Checkly then issues a TLS certificate for your domain and renews it automatically. Custom domains are available on Communicate Starter, Team and Enterprise @@ -15,6 +15,8 @@ You can host your status page on your own domain. To set it up, add the domain i ![Custom domain configuration](/images/docs/images/status-pages/status-pages-custom-domain-1.png) + +Save your status page. Checkly then lists the DNS records your domain needs below the custom domain field. @@ -26,14 +28,29 @@ You can host your status page on your own domain. To set it up, add the domain i should always be set to DNS only. - -After you've added your custom domain and saved the page, one or more TXT records will be displayed depending on the domain you're using. + +New domains are validated over HTTP, so the CNAME record is usually all you need. If Checkly shows TXT records for your domain, add them to your DNS configuration as well. ![Example custom domain TXT configuration](/images/docs/images/status-pages/status-pages-custom-domain-3.png) -Update your DNS settings to match the TXT record(s) displayed on your status page to prove the ownership of the domain. - - -Search engines require this verification to index and list your status page. - +Select **Refresh domain status** to check your setup. Once your DNS is set up, issuing the certificate usually takes a few minutes. A green check next to the custom domain field means your domain is verified. + +## Certificate renewal and troubleshooting + +Checkly renews the certificate for your custom domain automatically. Domains validated over HTTP need no DNS changes to renew, as long as the CNAME record keeps pointing to `custom-domain.checkly-status-page.com`. Don't remove or change that record while the status page uses your domain. + +If your domain has CAA records, they must allow the certificate authority named in the error message in Checkly. + +If something goes wrong, the status page settings show one of these messages below the custom domain field: + +| Message | What to do | +|---------|------------| +| "Certificate validation failed: …" | The certificate couldn't be validated. Fix the reason given in the message, then select **Refresh domain status**. | +| "Your domain's CAA records do not allow our certificate authority to issue a certificate." | Remove the CAA records on your domain, or add `0 issue "pki.goog; cansignhttpexchanges=yes"` alongside your existing policy. Then select **Refresh domain status**. | +| "Certificate issuance timed out for this domain." | Select **Refresh domain status** to start a new certificate order. | +| "Cloudflare has not returned the certificate validation records yet." | Wait a moment, then select **Refresh domain status** to check again. | + +If refreshing doesn't help, remove the custom domain from your status page, save, then add it again and save. + +If a certificate can't be issued or renewed, for example because the CNAME record no longer points to Checkly or the certificate is about to expire, Checkly emails the owners and admins of your account. From b871147b65a0ea4313bd4c616966843d5332a563 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Fri, 6 Nov 2026 21:20:57 -0500 Subject: [PATCH 2/5] docs: drop unverified certificate email sentence Co-Authored-By: Claude Opus 5.5 --- communicate/status-pages/custom-domain.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index 882948da7..d8f15e2dc 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -52,5 +52,3 @@ If something goes wrong, the status page settings show one of these messages bel | "Cloudflare has not returned the certificate validation records yet." | Wait a moment, then select **Refresh domain status** to check again. | If refreshing doesn't help, remove the custom domain from your status page, save, then add it again and save. - -If a certificate can't be issued or renewed, for example because the CNAME record no longer points to Checkly or the certificate is about to expire, Checkly emails the owners and admins of your account. From b5fb50e230543946cc190caec180433ea04690f2 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sat, 7 Nov 2026 16:16:18 -0500 Subject: [PATCH 3/5] Apply suggestion from @hlenke --- communicate/status-pages/custom-domain.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index d8f15e2dc..a42ad88a1 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -38,7 +38,7 @@ Select **Refresh domain status** to check your setup. Once your DNS is set up, i ## Certificate renewal and troubleshooting -Checkly renews the certificate for your custom domain automatically. Domains validated over HTTP need no DNS changes to renew, as long as the CNAME record keeps pointing to `custom-domain.checkly-status-page.com`. Don't remove or change that record while the status page uses your domain. +Checkly renews the certificate for your custom domain automatically. Domains validated over HTTP need no DNS changes to renew, as long as the CNAME record keeps pointing to `custom-domain.checkly-status-page.com`. Don't remove or change that record while the status page uses your domain. If your domain was set up with TXT records and Checkly shows new TXT records, add them, then select **Refresh domain status**. If your domain has CAA records, they must allow the certificate authority named in the error message in Checkly. From 0b3206a4708d270c81f579b0080e6926f7765cc0 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sat, 7 Nov 2026 16:16:49 -0500 Subject: [PATCH 4/5] Apply suggestion from @hlenke --- communicate/status-pages/custom-domain.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index a42ad88a1..75254a298 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -40,7 +40,7 @@ Select **Refresh domain status** to check your setup. Once your DNS is set up, i Checkly renews the certificate for your custom domain automatically. Domains validated over HTTP need no DNS changes to renew, as long as the CNAME record keeps pointing to `custom-domain.checkly-status-page.com`. Don't remove or change that record while the status page uses your domain. If your domain was set up with TXT records and Checkly shows new TXT records, add them, then select **Refresh domain status**. -If your domain has CAA records, they must allow the certificate authority named in the error message in Checkly. +If your domain has CAA records, they must allow the certificate authority `pki.goog`, which issues your status page certificate. If something goes wrong, the status page settings show one of these messages below the custom domain field: From bb4fc633a4142e546da48460c34aa9b9a46ef254 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Sat, 7 Nov 2026 16:17:26 -0500 Subject: [PATCH 5/5] Apply suggestion from @hlenke --- communicate/status-pages/custom-domain.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/communicate/status-pages/custom-domain.mdx b/communicate/status-pages/custom-domain.mdx index 75254a298..b5186d4ea 100644 --- a/communicate/status-pages/custom-domain.mdx +++ b/communicate/status-pages/custom-domain.mdx @@ -47,6 +47,7 @@ If something goes wrong, the status page settings show one of these messages bel | Message | What to do | |---------|------------| | "Certificate validation failed: …" | The certificate couldn't be validated. Fix the reason given in the message, then select **Refresh domain status**. | +| "Cloudflare reported a certificate validation failure for this domain." | Select **Refresh domain status**. If the message stays, contact [support@checklyhq.com](mailto:support@checklyhq.com). | | "Your domain's CAA records do not allow our certificate authority to issue a certificate." | Remove the CAA records on your domain, or add `0 issue "pki.goog; cansignhttpexchanges=yes"` alongside your existing policy. Then select **Refresh domain status**. | | "Certificate issuance timed out for this domain." | Select **Refresh domain status** to start a new certificate order. | | "Cloudflare has not returned the certificate validation records yet." | Wait a moment, then select **Refresh domain status** to check again. |