A Certificate as a Service (CaaS) request only gives you an SSL Certificate once every requirement has been met. The SSL Certificate is issued the moment the checks are complete, which usually takes a few minutes.
If no SSL Certificate arrives within a few minutes, one of those checks has not passed. The cause is almost always one of the checks described below, not a problem with your license or your order. Learn About Certificate as a Service (CaaS) 🔗
The Difference Between Acceptance and Issuance
An Automatic Certificate Management Environment (ACME) client is the software on your server that requests an SSL Certificate and installs it for you. When it sends a request, a reply that the request was accepted only means the order reached the Certificate Authority (CA).
It does not mean an SSL Certificate has been issued. That happens only after the Certificate Authority (CA) has confirmed that you control each domain name and that every required check has passed. Until then you have no SSL Certificate, even though the request went through.
Note : An accepted request and an issued SSL Certificate are not the same thing. The SSL Certificate appears only after every check has passed, so if you have no SSL Certificate, at least one check has not passed yet.
The sections below cover the checks that must pass. Each one is automatic, and any single failure is enough to stop the SSL Certificate from being issued.
Domain Control Validation (DCV) Must Complete
Every SSL Certificate confirms that you control the domain names you asked to secure. Your Automatic Certificate Management Environment (ACME) client proves this by placing a validation record for the Certificate Authority (CA) to find, either in your Domain Name System (DNS) or in a file on your website.
If that record is missing, wrong, or cannot be reached when the Certificate Authority (CA) looks for it, the check fails and no SSL Certificate is issued. Removing the record too soon, or never adding it, is a common reason.
Root and www Coverage
If your request covers both your main domain and its www version, the record is needed for each one. A record for only one of them leaves the other unproven, and the SSL Certificate is not issued. Learn About Keeping Validation Records in Place 🔗
Certification Authority Authorization (CAA) Checks
A Certification Authority Authorization (CAA) record is an optional Domain Name System (DNS) record that lists which Certificate Authorities may issue SSL Certificates for your domain name. You do not need one, and with no record in place any Certificate Authority (CA) is allowed to issue.
What matters is that the Certificate Authority (CA) can reach your Domain Name System (DNS) server and read the result from more than one location. If your Domain Name System (DNS) server cannot be reached from each location the check uses, the check is treated as a failure, whether or not a record exists.
Where a record is present, it must include the Certificate Authority (CA) that is issuing your SSL Certificate. A record that authorizes one Certificate Authority (CA) but not the issuing one is a frequent cause of a refused request. Learn About Certification Authority Authorization (CAA) Records 🔗
Multi-Perspective Issuance Corroboration (MPIC) Checks
Multi-Perspective Issuance Corroboration (MPIC) means the Certificate Authority (CA) checks your domain name from several places on the internet, not just one. This makes it much harder for anyone to interfere with the check from a single location.
If your domain name or server cannot be reached from some of those places, or answers differently depending on where the check comes from, the checks do not agree and the SSL Certificate is not issued.
Common causes are Domain Name System (DNS) records that are still spreading across the internet, a Domain Name System (DNS) server that is not reachable everywhere, or a server that blocks visitors from certain regions. Learn About Multi-Perspective Issuance Corroboration (MPIC) 🔗
Domain Name System Security Extensions (DNSSEC) Configuration
Domain Name System Security Extensions (DNSSEC) add digital signatures to your Domain Name System (DNS) records, so that others can confirm the records are genuine. When it is set up correctly, it protects your domain name.
When Domain Name System Security Extensions (DNSSEC) are turned on but set up incorrectly, the Certificate Authority (CA) cannot read your validation record at all, even though it may still work for you. The request then fails, often without a clear reason. Learn About Domain Name System Security Extensions (DNSSEC) 🔗
Rate Limiting and Repeated Requests
If you send many requests for the same domain name in a short time, the Certificate Authority (CA) may apply a rate limit. It then waits before checking again, or holds off on further checks, until enough time has passed.
Sending more requests does not make the SSL Certificate arrive sooner. It usually makes the wait longer, because each new request adds to the rate that caused the limit.
Warning : Resubmitting a request that is not issuing will not force an SSL Certificate to appear. It usually triggers a rate limit and makes the wait longer, while the real problem stays unfixed.
It is better to fix the real problem first, give any Domain Name System (DNS) changes time to take effect, and then let your client try again on its normal schedule. Learn About Validation Delays From DNS Configuration 🔗
What Your ACME Client Reports
Your Automatic Certificate Management Environment (ACME) client shows most refusals, because the Certificate Authority (CA) sends back an error with a short description that the client displays. A Certification Authority Authorization (CAA) refusal and a rate limit both arrive this way.
A Certification Authority Authorization (CAA) refusal is reported as the request not being authorized.
When a request is refused, the client marks it as failed and stops. If it runs on a schedule, it tries again at its next run, and every failed attempt still counts toward the rate limit, so it is better to fix the cause than to keep trying.
Some problems show little detail. A Domain Name System Security Extensions (DNSSEC) fault, or a Domain Name System (DNS) lookup that fails, can leave the Certificate Authority (CA) unable to tell whether it is allowed to issue, so you see only a general lookup error.
When that happens, the fact that no SSL Certificate arrived is the clearest sign that something still needs fixing.
Organization Validation (OV) Orders
Organization Validation (OV) under Certificate as a Service (CaaS) is handled separately, when you place the order, using a pre-validation reference. This confirms your organization details before any SSL Certificate is issued.
The domain name checks on this page still apply to every SSL Certificate, including Organization Validation (OV). Confirming your organization once does not remove the need to prove that you control the domain name on each request. Learn About Pre-Validation Reference Information 🔗
The License Remains Valid
Your license is separate from these checks. A request that cannot be validated gives you no SSL Certificate, but your license is not affected and can still issue once the requirements are met.
A request that does not issue is not refunded, because your license covers the cost rather than each individual SSL Certificate. Meeting the requirements is the responsibility of the license holder, and there is no charge to try again once the problem is fixed.
Confirming Your Eligibility
Checking these requirements is your responsibility, and you can confirm each one with the Domain Name System (DNS) tools in your own environment. Make sure your validation record is in place and correct for every name on the request, including both your main domain and its www version where both are covered.
Trustico® provides complimentary tools for checking and generating Certification Authority Authorization (CAA) records, and for checking Domain Name System (DNS) entries. Public tools can also show whether your records are visible from locations around the world. Explore Our SSL Certificate Tools 🔗
Confirm that your Domain Name System (DNS) server answers from more than one location, so the Certificate Authority (CA) can complete its checks, and that Domain Name System Security Extensions (DNSSEC), where you use it, resolves without errors.
Where you have a Certification Authority Authorization (CAA) record, confirm it authorizes the Certificate Authority (CA) that is issuing your SSL Certificate.
When validation is complete, which means the checks succeed from every location and your domain name is free of Domain Name System Security Extensions (DNSSEC) errors, the SSL Certificate will issue.
Confirming that this is true is your responsibility, and it is part of running a secure service online. Working through each requirement in turn clears nearly every case of non-issuance.