Skip to content
thenetworktools
Sign in

tool / caa

CAA Policy

Run a live check.

try

Workflow & Diagnostics

How CAA Policy works

Lock down SSL/TLS certificate issuance. Verify which Certificate Authorities are authorized to sign certificates for your domain, and prevent rogue issuance.

1

Enter your domain name.

2

Review live published CAA records and authorized Certificate Authorities.

3

Use the interactive generator to customize allowed CAs and copy instant DNS records.

Specifications & Scope

About CAA Policy

01 / What it does
Lock down SSL/TLS certificate issuance. Verify which Certificate Authorities are authorized to sign certificates for your domain, and prevent rogue issuance.
02 / How to use
1. Enter your domain name. 2. Review live published CAA records and authorized Certificate Authorities. 3. Use the interactive generator to customize allowed CAs and copy instant DNS records.
03 / Good to know
If you use Let's Encrypt with Cloudflare or AWS ACM, add issue records for all active providers to avoid automated renewal disruptions.

Got Questions?

Frequently Asked Questions

Certification Authority Authorization (RFC 8659) tells public CAs which providers are allowed to issue certificates for your domain.
Technical Reference & Standards

Tool Details & Usage Guide

RFC specifications, input expectations, outputs, and edge limitations.

What is a CAA Record?

Certification Authority Authorization (CAA), defined in RFC 8659, is a specialized DNS resource record (Type 257) that allows domain owners to declare which public Certificate Authorities (CAs) are permitted to issue SSL/TLS certificates for their hostnames.

Before issuing any certificate, public CAs (such as Let’s Encrypt, DigiCert, Google Trust Services, or Sectigo) are mandatory-required by the CA/Browser Forum to check DNS for CAA records. If a CAA record is published and the CA is not explicitly listed, the CA must refuse to issue the certificate.

The Three RFC 8659 Tags

A CAA record consists of three elements: flags, tag, and value.

  1. issue: Authorizes specific CAs to issue single-domain, multi-domain, or wildcard certificates (e.g. 0 issue "letsencrypt.org").
  2. issuewild: Overrides issue specifically for wildcard certificates (*.domain.com). Setting 0 issuewild ";" strictly forbids any CA from issuing wildcard certificates.
  3. iodef: Specifies an incident reporting email or URL where CAs must report unauthorized certificate issuance attempts (e.g. 0 iodef "mailto:[email protected]").

Why You Must Publish CAA Records in 2026

  • Defend Against Rogue Certificate Issuance: If an attacker compromises an obscure CA or steals DNS credentials, CAA records stop unauthorized CAs from issuing fake valid SSL certificates.
  • Enforce Corporate PKI Compliance: Prevent developers or external vendors from using unauthorized third-party CAs on corporate domains.
  • Instant Security Violation Alerts: With iodef, your security operations team is automatically alerted whenever an unauthorized party attempts to request a certificate for your domain.