Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

CAA record planning: control which certificate authorities may issue for a domain

Published August 2026 · 2 min read · Updated 2026-09-05

CAA records tell certificate authorities which CAs are authorized to issue certificates for a domain. They are a policy signal, not a replacement for domain validation. A restrictive CAA set can also break automated renewal if the issuing CA or account-specific requirement is not represented.

Inventory who issues certificates today

Find the CA used by the web host, CDN, reverse proxy, mail server, control panel, API gateway, and any external service that terminates TLS for your domain. A domain can legitimately have certificates from more than one CA.

Do this before publishing a restrictive CAA policy so renewal does not fail weeks later.

Understand issue, issuewild and reporting tags

The issue property controls ordinary certificate issuance; issuewild can apply separately to wildcard certificates. Some CAs support account binding or incident-reporting parameters, but syntax and support should be verified against current CA documentation.

An empty authorization value can intentionally prohibit a class of issuance, so copy examples carefully.

Remember inheritance

CAA lookup can inherit policy from a parent label when a subdomain has no CAA record of its own. Delegated or third-party subdomains therefore deserve explicit review when their TLS service is managed elsewhere.

A CNAME can also affect where CAA processing looks, depending on the issuance scenario.

Test renewal before relying on the policy

After publishing CAA, trigger or stage certificate issuance for the services you depend on, verify public DNS from authoritative servers, and monitor renewal logs.

  • List every legitimate certificate issuer.
  • Separate wildcard policy where needed.
  • Review inheritance and delegated services.
  • Test automated renewal after changes.

Next step

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

See the DotMoose security approach

Keep reading

Related guides.

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

DMARC alignment troubleshooting: find why SPF or DKIM passes but DMARC fails

Compare From, Return-Path and DKIM signing domains, relaxed or strict alignment and forwarding behaviour to diagnose a DMARC alignment failure.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move