Skip to content

CAA Records 2026: Adoption Benchmark

Key idea:

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.

Key Findings

MetricPass / ValueMedianp75
Domains with a CAA record14%
CAA with iodef (incident email)7%
CAA with accounturi (CA account binding)2%
Let's Encrypt in CAA48%
DigiCert in CAA18%
Sectigo in CAA14%
GlobalSign in CAA8%
Misconfigured CAA (blocks valid renewal)0.3%

Breakdown by Platform

PlatformShareDetail
REG.RU DNS28% marketCAA support: Yes (UI since 2024)
Cloudflare DNS14%CAA support: Yes (UI)
Timeweb DNS11%CAA support: No UI (2026)
Beget DNS9%CAA support: No UI
Yandex Cloud DNS7%CAA support: Yes
Self-hosted BIND/PowerDNS4%CAA support: Full

Why It Matters

  • CAA protects against mis-issuance: if an attacker compromises DNS without CAA, they can get a cert from any CA
  • Chrome/Firefox don't check CAA (that's the CA's job at issuance), so CAA doesn't break existing clients
  • Let's Encrypt checks CAA on every renewal — a bad record can break auto-renew
  • iodef= email lets the CA notify the owner about mis-issuance attempts
  • CAA doesn't replace DNSSEC — they are complementary (DNSSEC protects the DNS answer, CAA sets policy for CAs)

Methodology

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.

A / AAAAIPv4 and IPv6 host addresses
MX RecordsDomain mail servers
TXT / SPFVerification & anti-spoofing
NS / SOAName servers & zone authority

Why teams trust us

12
DNS record types
SPF+DKIM
email protection
<1s
DNS response
3
check regions

How it works

1

Enter domain

2

Select record type

3

Get DNS response

What are DNS Records?

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.

Complete Lookup

Query all record types — A, AAAA, MX, NS, TXT, CNAME, SOA — in a single request.

Instant Results

Direct queries to authoritative servers. Results in milliseconds, no caching.

Security Checks

SPF, DKIM, and DMARC analysis to evaluate email protection against spoofing and phishing.

Export & History

Save check results. Compare DNS records before and after registrar changes.

Who uses this

DevOps

DNS check after deploy

Email marketers

SPF/DKIM/DMARC audit

SEO

DNS config audit

Sysadmins

DNS zone control

Common Mistakes

Missing SPF recordWithout SPF, emails may land in spam. Add a v=spf1 TXT record.
Single NS serverIf the only NS fails, the domain becomes unreachable. Use at least 2 NS servers.
CNAME conflicting with other recordsCNAME cannot coexist with MX or TXT on the same name — this violates RFC.
TTL set too highWith 86400s TTL, DNS changes take a full day. Lower TTL to 300 before migrations.
Missing PTR recordMail servers check PTR. Without it, emails may be rejected.

Best Practices

Set up SPF + DKIM + DMARCThe trio of records that protects your email from spoofing and improves deliverability.
Use 2+ NS serversDistribute NS servers across different networks for redundancy.
Lower TTL before migrationSet TTL to 300 at least 24-48 hours before an IP change for fast propagation.
Verify DNS after changesAfter updating records, confirm changes propagated correctly and no errors remain.
Add a CAA recordCAA restricts which Certificate Authorities can issue SSL certificates for your domain.

Get more with a free account

DNS check history, API keys and DNS change monitoring.

Sign up free

Learn more

Frequently Asked Questions

Is CAA required?

No, not required but recommended. Without CAA any CA can issue a cert for your domain (given successful domain validation).

How do I add a CAA record?

In DNS zone: <code>example.com. IN CAA 0 issue "letsencrypt.org"</code>. Wildcard: <code>0 issuewild "letsencrypt.org"</code>.

What if CAA blocks a legitimate CA?

Clear cache on CA accounts + add CAA for the new CA. Propagation is usually 1-24 hours.

How to check my CAA?

<a href="/en/dns">Enterno DNS</a> → type CAA. Or <code>dig CAA example.com</code>.