CAA record
A DNS record naming the certificate authorities allowed to issue for this domain. Optional hardening: without it, any authority may issue.
A CAA (Certification Authority Authorization) record lists the certificate authorities that may issue TLS certificates for your domain. Every public CA is required to check it before issuing: if your domain says only Let's Encrypt may issue, any other CA must refuse a request — even one from someone who has managed to pass domain validation by other means.
How SiteScan checks
The scan looks up CAA records on the registrable domain. If any exist, the row is green and shows how many. If none exist, the row reads "Missing" in a neutral state: without CAA every CA may issue, which is the default for most of the web and not a defect. CAA is optional hardening.
How to add it
Find out which CA issues your certificates today — the certificate issuer row shows it — and publish one record per authority, for example:
example.com. CAA 0 issue "letsencrypt.org"example.com. CAA 0 issuewild ";"to forbid wildcard certificatesexample.com. CAA 0 iodef "mailto:security@example.com"for violation reports
Remember to include every service that obtains certificates for you: a CDN, a hosted shop or an email provider may use a different CA. A forgotten one will make its next renewal fail. Subdomains inherit the records unless they publish their own.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “DNS & email”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data