Site Sentinel can report an expired certificate, one nearing expiry or a certificate that does not cover the checked hostname. Use those findings to direct a certificate review, not as a substitute for the website’s normal TLS checks.

Check the finding and target

1. Open PD Modules → Site Sentinel → Needs attention and locate the certificate finding.
2. Confirm the intended site hostname and Scanned time in Sites.
3. Check Check the certificate in Settings.
4. Review the site’s certificate through your normal browser or hosting administration tools. Do not bypass a browser security warning to continue browsing.

The module flags expiry within 21 days. Its stored expiry is a date and can differ from a precise certificate timestamp around the expiry day. Compare the actual certificate validity before diagnosing the exact cut-off.

Repair at the website

Renew or replace the certificate through the site’s normal hosting controls and ensure the intended hostname is covered. Changing or accepting the Site Sentinel finding does not install a certificate.

After the website change, arrange another relevant scan and confirm that site’s timestamp advanced. Scan now processes a batch, so the click alone does not prove the affected site was rechecked.

Understand what is not verified

The scanner needs a successful home-page response before this check runs. It inspects certificate expiry and hostname information, not a complete browser trust-chain or revocation assessment. Redirected sites can make the original hostname and final page host differ. Missing certificate data or a cleared finding is not proof of a fully valid HTTPS setup.

See the PD Site Sentinel Blesta guide for related tasks, or explore PD Site Sentinel.