CAA (Certificate Authority Authorization) violation — the domain's DNS CAA record does not permit the specified CA to issue a cert. Let's Encrypt, DigiCert and others check CAA before issuance. If CAA says "only digicert.com" and you request from Let's Encrypt — refuse. Fix: add the CA to CAA or remove the CAA record.
Below: causes, fixes, FAQ.
issuewild) does not authorise CA for wildcard certs; in value — syntax error, effectively "no CA allowed"example.com. IN CAA 0 issue "letsencrypt.org"example.com. IN CAA 0 issuewild "letsencrypt.org"SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freeRemove all CAA records. Any CA may issue. CAA is optional — no constraints by default.
The CA before issuance (mandatory for public CAs since 2017). Browsers do not check CAA.
No. iodef is an email for notifications on mis-issuance attempts. Useful but optional.
<a href="/en/dns">Enterno DNS</a> → CAA type. Or <code>dig CAA example.com</code>.