Free CAA Records Checker

Free CAA Records Checker

Free tool

Validate CAA DNS records to control which Certificate Authorities can issue certificates for your domain. Prevents unauthorized cert issuance and domain hijacking.

  • CAA record validation and analysis
  • Certificate Authority authorization check
  • Wildcard and subdomain CAA coverage
No credit card requiredProduction-safe (100% passive)No setup or code required
Trusted by 4,000+ security & engineering teams
Oracle logoShopify logoGoDaddy logoChubb logoToshiba logoMAPFRE logoBelfius logoGBG logoWEKA logoShift Technology logo

What you get for free

18 core security checks via this tool, passive scans, step-by-step remediation, security score on every result.

What Essential adds at $39/mo

+17 advanced checks, continuous monitoring, daily security score history, email alerts, GitHub SAST, board-ready PDFs, SOC 2 / ISO 27001 / PCI reports.

What this checker validates

  • Presence and configuration of CAA records
  • Authorized Certificate Authorities list
  • Wildcard and subdomain CAA coverage
  • CAA record syntax and policy compliance
  • Certificate issuance policy validation

What are CAA Records?

CAA (Certificate Authority Authorization) records are DNS records that specify which Certificate Authorities (CAs) are authorized to issue SSL/TLS certificates for your domain. This helps prevent unauthorized certificate issuance and domain hijacking attacks.

How to configure CAA Records

  • Basic CAA: 0 issue "letsencrypt.org" (allow Let's Encrypt)
  • Restrictive CAA: 0 issue "digicert.com" (only DigiCert)
  • Wildcard CAA: 0 issuewild "sectigo.com" (wildcard certs only from Sectigo)
  • Report-only: 0 iodef "mailto:security@example.com" (report violations)

Benefits of CAA Records

  • Prevents unauthorized certificate issuance by malicious CAs
  • Reduces risk of domain hijacking and phishing attacks
  • Provides audit trail for certificate issuance
  • Enhances overall domain security posture
  • Compliance with security best practices

Implementation examples

Once you've identified the gap, applying the fix is straightforward. Here are the three configurations developers reach for most often.

BIND zone file

example.com.   IN  CAA  0 issue "letsencrypt.org"
example.com.   IN  CAA  0 issuewild ";"
example.com.   IN  CAA  0 iodef "mailto:security@example.com"

Cloudflare API

{
  "type": "CAA",
  "name": "example.com",
  "data": { "flags": 0, "tag": "issue", "value": "letsencrypt.org" },
  "ttl": 3600
}

AWS Route 53

{
  "Name": "example.com.",
  "Type": "CAA",
  "TTL": 3600,
  "ResourceRecords": [
    { "Value": "0 issue \"letsencrypt.org\"" },
    { "Value": "0 issuewild \";\"" },
    { "Value": "0 iodef \"mailto:security@example.com\"" }
  ]
}

Tool-specific questions

Are CAA records mandatory?

CAA records are not mandatory, but they are a security best practice. They provide an additional layer of protection against unauthorized certificate issuance.

What happens if I don't have CAA records?

Without CAA records, any Certificate Authority can potentially issue certificates for your domain, increasing the risk of unauthorized certificate issuance.

Can I have multiple CAA records?

Yes, you can have multiple CAA records to authorize multiple Certificate Authorities or set different policies for different types of certificates.

How do CAA records affect wildcard certificates?

Use the 'issuewild' tag to control wildcard certificate issuance separately from regular certificates. This provides granular control over certificate types.

Should I monitor CAA records regularly?

Yes, regular monitoring ensures your CAA records remain properly configured. Use Barrion's continuous monitoring to track CAA record status and detect any changes.
Why Barrion

Built for the engineers who already have enough to fix.

Speed

Real-time results

Instant analysis with a detailed report. You see findings as the scan runs, not after.
Coverage

Comprehensive checks

35+ checks per scan covering TLS, headers, CORS, cookies, DNS, email auth, and more, in a single pass.
Action

Step-by-step fixes

Every finding ships with the exact remediation step for your framework. Hand it to the engineer who owns the surface.
FAQ

Frequently asked.

What is Barrion and how does it enhance website security?
Barrion is a security testing and monitoring platform for engineering teams, and it works in three ways. Passive scanning keeps a continuous, read-only watch over your live web apps and APIs. Codebase scanning connects to GitHub and checks your code for hard-coded secrets, insecure patterns and vulnerable dependencies. AI pentesting goes on the offensive, running agent-driven attacks that prove which vulnerabilities are genuinely exploitable. Every finding comes with a step-by-step fix you can ship right away.
How safe is Barrion to use for security testing?
Passive scanning and codebase scanning are completely safe to run, including against production. Passive scans only read your live app, so we never submit forms, brute-force endpoints or touch anything that changes state, and codebase scanning just reads your repository. AI pentesting is more aggressive by design, since its job is to confirm real exploits, so it runs rate-limited and non-destructive, and you agree the scope with us before it starts.
What types of security issues does Barrion identify?
It depends on the surface. On your live apps, Barrion catches misconfigurations across TLS and HTTPS, security headers, cookie flags, CORS policy, DNS records, email authentication (SPF, DKIM, DMARC), network exposure and the usual web hygiene gaps. In your codebase it finds secrets committed to the repo, insecure code patterns and vulnerable dependencies. AI pentesting surfaces the exploitable stuff, like SQL injection, cross-site scripting and broken access control, each one backed by proof it can actually be exploited.
What specific security checks does Barrion perform?
For live apps it checks TLS and HTTPS configuration, HTTP security headers, cookie flags, CORS policy, DNS and email authentication records, network exposure and common web hygiene issues. In your codebase it looks for hard-coded secrets, insecure patterns and vulnerable dependencies. AI pentesting takes it further by actively chaining requests to confirm exploitable flaws. Whatever the source, findings are ranked by severity and come with clear, step-by-step remediation.
What is Barrion's smart crawling?
Smart crawling automatically discovers the pages and endpoints of your app so scans cover the surface that matters, without you manually listing every URL.
How often does Barrion perform security scans?
You can run a scan manually whenever you want. Continuous monitoring of your live apps runs on its own (weekly and up on Essential, daily on Business), codebase scans can fire on every commit or pull request, and we alert you the moment something new shows up.
Is Barrion suitable for security testing of all business sizes?
Yes. Live-app monitoring, codebase scanning through GitHub and AI pentesting all work just as well for a solo developer as for a startup, a scale-up or an enterprise security team, without adding headcount.
How does Barrion handle data security and privacy during security testing?
Live-app and codebase scans are read-only by default, and we never store or expose sensitive data from your application. AI pentests are rate-limited and non-destructive, built to confirm whether something is exploitable without altering your data or affecting availability.
What if I'm not satisfied with Barrion's security testing service?
Paid plans start with a free trial, and you can cancel anytime. If something isn't right, contact us and we'll make it work for your team.
How does Barrion help with SOC 2, ISO 27001, NIS2, and other compliance frameworks?
Barrion produces audit-ready PDF and CSV reports suitable for SOC 2, ISO 27001, PCI DSS and NIS2, ready to share with auditors, customers and your board.

Anything else? Email contact@barrion.io.

Run a full report on your site.

Free first scan covers every check, no signup needed. Sign up to save the report and turn on continuous monitoring.