Free CAA Records Checker
Free tool
Check whether your domain publishes CAA DNS records, which control which Certificate Authorities can issue certificates for it. Helps prevent unauthorized cert issuance.
- CAA record presence check
- Example records for common CAs
- Fix guidance
No credit card requiredRead-only, no exploitationNo setup or code required
Used by 5,000+ developers and engineering teams
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 from €199/mo
Pentest credits every month, +17 advanced checks, weekly passive scans, email alerts and audit-ready PDFs for SOC 2 / ISO 27001 / PCI.
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.
What this checker looks at
- Whether your domain publishes any CAA records
- It doesn't check the CA list, record syntax or wildcard policy, so review those in your DNS provider
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)
- Violation reports: 0 iodef "mailto:security@example.com" (where CAs report refused requests)
Benefits of CAA Records
- Prevents unauthorized certificate issuance by malicious CAs
- Makes it harder to get a rogue certificate for phishing
- Enhances overall domain security posture
- Compliance with security best practices
Implementation examples
CAA records are added like any other DNS record, straight from your DNS provider's dashboard. Add these three at the root of your domain, replacing letsencrypt.org with whichever CA actually issues your certificates:
| Type | Name / Host | Value |
|---|---|---|
| CAA | @ | 0 issue "letsencrypt.org" |
| CAA | @ | 0 issuewild ";" |
| CAA | @ | 0 iodef "mailto:security@example.com" |
Some dashboards (Cloudflare, Route 53) split the value into separate flag, tag, and value fields instead of one string: flag is 0, the tag is issue, issuewild, or iodef, and the value is the CA domain or mailto address. The issuewild line with ";" blocks wildcard certificates entirely, so drop it if you use them.
Self-hosted DNS (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"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
Fast results
Instant analysis with a detailed report. You see findings as the scan runs, not after.
Coverage
Comprehensive checks
The full passive scan runs 18 checks on the free plan, covering TLS, headers and cookies. Paid plans run 35+ and add CORS, DNS, email auth and more.
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.
Other tools
More free checks, for the rest of your surface.
Complete Security Scan
Complete website security analysis with comprehensive vulnerability detection
Pre-Pentest Security Scan
Passive scan that catches the misconfigurations a pentester finds first. Use it before a manual engagement to clear the easy issues.
Security Compliance Checker
Run general security checks relevant to PCI DSS, HIPAA, SOC 2, ISO 27001 and GDPR. Findings aren't mapped to specific requirements.
WAF Checker
Detect which WAF or CDN sits in front of your site from the signatures in its response. Passive, no attack payloads.
Security Headers Test
Check your website's HTTP security headers configuration
TLS/SSL Security Checker
Validate your SSL/TLS configuration and certificate setup
FAQ
Frequently asked.
What is Barrion?
Barrion runs continuous, agentic AI penetration tests of web applications and APIs. AI agents test your app the way an attacker would, safely, on a schedule or on demand. Findings are checked against the live app before they're reported, and tracked across runs as new, still open, resolved or regressed. From Standard level up, a security engineer reviews each report. Barrion AB is based in Gothenburg, Sweden. A free passive scan is the quickest way to start.
How safe is Barrion to use for security testing?
AI pentests send real test requests, so they're rate-limited and non-destructive, and you approve the exact scope before a single request goes out. You can point them at staging too. The free passive scan only reads your live app. It never submits forms, brute-forces endpoints or touches anything that changes state, so it's safe to run against production.
What types of security issues does Barrion identify?
AI pentests look for the issues an attacker could exploit, like SQL injection, cross-site scripting and broken access control. Findings are checked against your live app, and confirmed ones come with the request and response that prove them. Anything we couldn't confirm is clearly marked and capped in severity. The passive scan catches misconfigurations in TLS and HTTPS, security headers, cookie flags, CORS policy, DNS records, email authentication (SPF, DKIM, DMARC) and network exposure.
What specific security checks does Barrion perform?
Barrion covers two surfaces. AI pentesting is the active part: specialist agents chain requests to find exploitable flaws such as SQL injection, cross-site scripting and broken access control. Findings are checked against your live app, and confirmed ones come with the request and response that prove them. The passive scan is read-only and safe to point at production. On paid plans it runs 35+ checks (18 on the free plan): transport security (HTTPS, HSTS, TLS version, cipher suites, certificate expiry, hostname and chain validity, OCSP stapling), HTTP response headers (Referrer-Policy, Permissions-Policy, X-Content-Type-Options, Content-Type, server information disclosure), CSP and framing (Content-Security-Policy, bypass detection, Trusted Types, X-Frame-Options), cross-origin policy (COOP, COEP, CORP and the full CORS header set), cookie flags and anti-CSRF tokens, mixed content, vulnerable JavaScript libraries, DNS records including DNSSEC and CAA, email authentication (SPF, DKIM, DMARC), open ports and subdomain takeover. Findings from both are ranked by severity and come with step-by-step remediation.
Will our auditor or enterprise customer accept the report?
The report maps every finding to OWASP WSTG, a security engineer reviews it from Standard up and signs it off from Deep up, and a free retest shows what you fixed. Teams use it as evidence for SOC 2, ISO 27001 and NIS2 work. Whether it's accepted is up to your auditor.
How often does Barrion test my app?
Continuously or on demand. On the Business plan you save a pentest and it reruns daily, weekly, monthly, quarterly, every six months, yearly or on your own rhythm. On any plan you can start a pentest or a passive scan on demand. A passive scan also runs on a schedule and alerts you when something new shows up.
Is Barrion suitable for security testing of all business sizes?
Yes. Solo developers often start with the free passive scan and a single pentest. Teams with several apps run pentests on a schedule, and it fits alongside the tools you already run.
How does Barrion handle data security and privacy during security testing?
Passive scans are read-only: they only look at what your app already exposes publicly. For AI pentests we store the findings and the evidence behind them, the requests and responses that confirm each issue, so you can review and reproduce them. Test credentials you add are encrypted. Data is stored and hosted in Sweden and AI processing runs in the EU. Our trust page lists every subprocessor. Pentests are rate-limited and only run inside the scope you approve.
What if I'm not satisfied with Barrion's security testing service?
You can cancel anytime in the dashboard, and paid plans carry a 14-day refund window from the first charge. 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's pentest reports come as PDF, XLSX and JSON, mapped to all 97 OWASP WSTG test cases, with engineer review from Standard up, sign-off from Deep up and a free retest after fixes. Teams use them as evidence that supports SOC 2, ISO 27001, PCI DSS and NIS2 work. Whether a report is accepted is up to your auditor or customer.
Anything else? Email contact@barrion.io.