CAA (Certificate Authority Authorization, RFC 6844) is a DNS record specifying which CAs may issue certs for your domain. Enterno.io checked top-5k .ru domains (March 2026): only **14%** use CAA (vs 32% in global top-1M). Reason: most RU registrars lack CAA editing UI. CA leaders inside CAA records: Let's Encrypt 48%, DigiCert 18%, Sectigo 14%.
Below: key findings, platform breakdown, implications, methodology, FAQ.
| Metric | Pass / Value | Median | p75 |
|---|---|---|---|
| Domains with a CAA record | 14% | — | — |
| CAA with iodef (incident email) | 7% | — | — |
| CAA with accounturi (CA account binding) | 2% | — | — |
| Let's Encrypt in CAA | 48% | — | — |
| DigiCert in CAA | 18% | — | — |
| Sectigo in CAA | 14% | — | — |
| GlobalSign in CAA | 8% | — | — |
| Misconfigured CAA (blocks valid renewal) | 0.3% | — | — |
| Platform | Share | Detail | — |
|---|---|---|---|
| REG.RU DNS | 28% market | CAA support: Yes (UI since 2024) | — |
| Cloudflare DNS | 14% | CAA support: Yes (UI) | — |
| Timeweb DNS | 11% | CAA support: No UI (2026) | — |
| Beget DNS | 9% | CAA support: No UI | — |
| Yandex Cloud DNS | 7% | CAA support: Yes | — |
| Self-hosted BIND/PowerDNS | 4% | CAA support: Full | — |
Top-5000 .ru domains by SimilarWeb ranking. DNS CAA queries via 1.1.1.1 and 8.8.8.8 (March 2026). CAA parser extracted issue= and iodef=. Registrar identified via WHOIS.
DNS (Domain Name System) translates domain names into IP addresses. DNS records are instructions that define where to route traffic, email, and how to verify domainownership.
Query all record types — A, AAAA, MX, NS, TXT, CNAME, SOA — in a single request.
Direct queries to authoritative servers. Results in milliseconds, no caching.
SPF, DKIM, and DMARC analysis to evaluate email protection against spoofing and phishing.
Save check results. Compare DNS records before and after registrar changes.
DNS check after deploy
SPF/DKIM/DMARC audit
DNS config audit
DNS zone control
v=spf1 TXT record.DNS check history, API keys and DNS change monitoring.
Sign up freeNo, not required but recommended. Without CAA any CA can issue a cert for your domain (given successful domain validation).
In DNS zone: <code>example.com. IN CAA 0 issue "letsencrypt.org"</code>. Wildcard: <code>0 issuewild "letsencrypt.org"</code>.
Clear cache on CA accounts + add CAA for the new CA. Propagation is usually 1-24 hours.
<a href="/en/dns">Enterno DNS</a> → type CAA. Or <code>dig CAA example.com</code>.