Skip to content

Can CAA Records Stop Blogger From Issuing or Renewing HTTPS Certificates?

A metal padlock beside two separated links of a chain.

If your Blogger custom domain uses CAA records, yes: Blogger says you must add a record for letsencrypt.org. Without it, Blogger will not create or renew the blog’s SSL certificate. That warning is conditional. It does not say that every HTTPS problem on a Blogger custom domain comes from CAA records.

Google states this requirement in its custom-domain setup guide and again in its HTTPS guide for Blogger. The two pages draw a useful line between connecting a domain, making HTTPS available, and redirecting visitors to HTTPS.

The CAA condition Blogger sets

Blogger’s wording is specific: the requirement applies when a custom domain uses CAA records. In that case, a record for letsencrypt.org is required for Blogger to create or renew the SSL certificate.

That means the warning has two parts:

  • The domain is a custom domain connected to a Blogger blog.
  • The domain uses CAA records.

When both conditions apply, the missing letsencrypt.org record can block certificate creation or renewal according to Google’s documentation. Google does not provide a universal CAA configuration in these pages, so copying a record syntax from an unrelated guide is a poor shortcut. The exact DNS interface and existing records belong to the domain provider.

A domain without CAA records falls outside the condition described in Blogger’s warning. That alone does not prove that its certificate will issue, renew, or become available at any particular time. The official pages do not make that promise.

Domain connection comes first

A custom domain must be connected in Blogger before its HTTPS settings matter. Google’s custom-domain guide tells users to enter the purchased domain under Settings and Custom domain in Blogger. If Blogger returns an error containing two CNAME records, Google lists two DNS tasks: a blog CNAME pointing to ghs.google.com and a second security CNAME that is unique to the blog and Google Account.

The security CNAME should not be replaced with an example from somebody else’s blog. Google says it is different for each person and specific to the blog and account.

Google also says DNS changes need time to activate and advises waiting at least one hour before repeating the Blogger setup. Separately, the guide says a blogspot.com address can take up to 24 hours to redirect to a custom domain. Those are two different statements. Neither one gives a certificate issuance or renewal deadline.

Question What Google’s Blogger pages establish
Is the custom domain connected? Blogger provides the custom-domain workflow and may request a blog CNAME plus a unique security CNAME.
Can Blogger create or renew the SSL certificate when CAA records exist? The custom domain needs a CAA record for letsencrypt.org.
Is HTTPS enabled in Blogger? For a custom domain, set HTTPS Availability to Yes.
Are visitors redirected to HTTPS? HTTPS Redirect is a separate setting that can be set to Yes.

This separation matters. A correct CAA requirement does not replace the CNAME steps needed to connect the custom domain. A connected domain does not automatically prove that HTTPS Availability is enabled. HTTPS Availability also does not answer whether HTTPS Redirect is turned on.

HTTPS Availability and HTTPS Redirect are separate switches

Google’s HTTPS instructions say that a custom-domain blog can enable HTTPS through Settings, under HTTPS Availability, by selecting Yes. The same page describes HTTPS Redirect as a separate setting under HTTPS Redirect.

HTTPS Availability concerns access over HTTPS. HTTPS Redirect concerns whether visitors are sent to the encrypted version of the blog. Google describes the redirect result as visitors reaching the blog at an https:// address.

For blogs that do not use a custom domain, Google says HTTPS is automatically turned on and the HTTPS setting is hidden. That statement does not remove the separate CAA condition for a custom domain using CAA records.

Keep the names of the settings straight while checking a problem. Turning on HTTPS Redirect cannot substitute for certificate creation. Turning on HTTPS Availability does not supply missing DNS records. Each setting has its own job.

What to check without blaming CAA too early

Start with the narrow question: does the custom domain use CAA records? If it does, check whether the required letsencrypt.org record is present in the domain’s DNS settings. Blogger’s documentation supports that check. It does not support assuming that a missing record is the cause before confirming that CAA records are actually in use.

Then review the connection details Blogger requested. Google’s domain guide says the blog CNAME uses the chosen subdomain, such as www, and points to ghs.google.com. It also says the second security CNAME is unique. A mismatch in either requested CNAME belongs to the custom-domain setup question, not automatically to the certificate question.

After that, check the Blogger settings themselves:

  • HTTPS Availability should be set to Yes for a custom-domain blog that should accept HTTPS.
  • HTTPS Redirect should be set to Yes only when visitors should be redirected to HTTPS.
  • A root-domain redirect, such as mydomain.com to www.mydomain.com, follows another setup path in Google’s custom-domain guide. Google lists four A records for that redirect and a separate Redirect domain setting.

For example, imagine a fictional blog at www.example.test. Its owner has entered the custom domain in Blogger, added the requested CNAME entries, and enabled HTTPS Availability. If that domain also uses CAA records, Blogger’s warning makes the letsencrypt.org requirement relevant. If the domain does not use CAA records, that specific warning does not identify the cause of any HTTPS issue.

The example does not establish what will happen for a real domain. The live DNS records, Blogger settings, and any message shown in the account remain the details to inspect.

What the official pages do not prove

Google’s two support pages do not diagnose an individual domain. They do not say that every unavailable HTTPS setting, browser warning, redirect problem, or custom-domain error has the same cause. They also do not publish a guaranteed wait time for certificate issuance or renewal.

They do establish one firm condition: a Blogger custom domain that uses CAA records needs a record for letsencrypt.org so Blogger can create or renew its SSL certificate.

That is the practical boundary. Check CAA when CAA exists. Check the requested CNAME values when domain connection is incomplete. Check HTTPS Availability and HTTPS Redirect as separate Blogger settings. Keep each check tied to the symptom you actually have.

Does your custom domain currently use CAA records? Has Blogger asked for the unique security CNAME, or is the domain already connected and only HTTPS is unavailable?