What it means
The certificate your server sends is still valid, but it ends in less than 14 days. The detail shows the exact number of days left for each host name.
Why it matters
When the date passes, every visitor sees a security warning and apps stop connecting. Certificates from automatic issuers such as Let's Encrypt normally renew about 30 days before they expire, so one this close usually means renewal has already failed at least once and will keep failing until someone looks.
How to fix it
- Renew the certificate now. With automatic certificates, run the renewal by hand; with a bought certificate, renew it with your authority and download the new files.
- Install the new certificate with its full chain and reload the web server.
- Find out why automatic renewal didn't happen. Common causes are a DNS challenge whose API key changed, an HTTP challenge blocked by a redirect or firewall, a server that moved, or renewal that writes a file the web server never reloads.
- Fix the cause, then run a dry run of the renewal to prove it works.
Let's Encrypt with certbot
sudo certbot renew --dry-run shows what would fail. Make sure a timer or cron job runs certbot renew and
that a deploy hook reloads your web server afterwards.
Hosting control panels
Most panels have an SSL or certificates page with a renew button and a log. If the domain's DNS moved elsewhere, the panel may no longer be able to prove you own the domain.
Check it worked
Run the SSL check again. The days left should now be around 60 to 90 for automatic certificates, or about a year for bought ones, and the finding should be gone.