Configure the CAA record. It's worth

Configure the CAA record. It's worth

13-11-2017 11:28:32

On September this year we have talked about the obligation for SSL certificate issuers to verify the CAA in client DNS records requesting SSL since September 8, 2017. If you are a webmaster now, there is an additional tool in your hands to protect you from invalid certificate issuance.

Low CAA popularity

Due to the buzz around the CAA in 2017, the number of deployments has increased significantly. SSL Pulse reports that the number of sites using CAA has doubled since September 2017, and has grown more than tenfold over the year. Even with this growth rate, only a few thousand websites use CAA, which is still a niche security mechanism ...

Why deploy CAA?

CAA is not just a safety mechanism. In addition to minimizing risk by limiting CAs certification to issuing certificates for your domain, CAA is also a useful tool for enforcing corporate policies related to SSL certificates. Many organizations are struggling to comply with their SSL purchase and deployment policies. This is particularly important in large organizations with many offices or branches.
If someone in your business creates a new service in your domain and requests a certificate, he or she will be able to use a limited list of approved offices. You can also set up a reporting URL or email address to receive notifications from CAs when they receive a request they can not fulfill.

How to implement a CAA record

Since most admins have not yet implemented the CAA, we have prepared a brief manual. CAA is a fairly easy-to-use mechanism and involves a significantly lower risk of configuration or operational errors than other mechanisms such as HSTS or HPKP. There is a technical precondition for using CAA. If you are using managed DNS, the provider must add CAA support because it is a new DNS resource record.
  • Specify which CA (Offices) are used by your organization. Create a list. If the list is to include "up to" 10 Offices it's still worth it;
  • Use list to enter CA to CAA record;
  • You can always update your CAA record if you want to change the list of Certification Authorities
  • Create a CAA DNS record.

Sample CAA record

A record that would allow DigiCert to issue certificates for a site: CAA 0 issue ""
This record would apply to all subdomains in the domain. If you want to authorize additional CAs, a new line will be created for each CA.

Recent Posts

Comodo / Sectigo is changing its Root CAs
28-12-2018 11:23:52

Sectigo, formerly known as Comodo CA, is entering the next phase of its transition: it’s replacing Comodo CA roots with USERTrust roots on January 14, 2019. Why it happens and what it will mean to Sectigo customers?

Comodo / Sectigo is changing its Root CAs
Comodo is now Sectigo
09-11-2018 12:54:30

According to previous announcements, a year after the acquisition of Comodo Group by Francisco Partners, on November 1 Comodo CA announced that from now on it is changing its brand to Sectigo [pronounced. sec-tee-go]. The goal of rebranding is consistency in company communication and better dedication to what Comodo is doing now.

Comodo is now Sectigo
European Cyber Security Month 2018
27-09-2018 10:46:21

The European Union Agency for Network and Information Security (ENISA), which is the center of knowledge about cyber security in Europe, organizes as every year in October the European Cyber Security Month. The campaign is starting in a few days. What is its purpose and how can you participate in it?

European Cyber Security Month 2018
more posts