Expired SSL Certificate

What it means

Your SSL certificate has expired. Visitors now get a full-page security warning instead of your site, and apps that call your API will fail to connect. This is distinct from a certificate that is merely approaching its expiry date — see the related finding below for that earlier warning stage.

Why it matters

An expired certificate is a hard trust failure, not a soft warning: browsers block the page behind an interstitial that most visitors will not click through, and machine clients (mobile apps, API integrations, webhooks) typically fail the connection outright with no visible warning to anyone until something downstream breaks.

What Nivaronix checks

Nivaronix reads the certificate's notAfter date during a TLS handshake. Once that date is in the past, this finding is raised at Critical severity. This is a certificate-expiry check, not a scan for vulnerabilities in the server software itself.

Example evidence

Illustrative example, not a live scan result. Run the checker below to see your own domain's actual status.

Illustrative example only — not a live scan result.

Certificate: CN=example.com
Issuer: Let's Encrypt Authority
Valid until: 4 days ago
Status: EXPIRED

How to fix it

• Renew your SSL certificate immediately.
• Issue a replacement certificate, install it, and reload the web server.
• If you use automatic renewal (certbot, acme.sh, or a platform-managed certificate), check why it stopped running before assuming it will renew itself next time.
• Once renewed, set an alert at least 30 days before the new expiry date so this doesn't recur.

How to verify the fix

Re-run the SSL/TLS checker against the domain, or open the site in a browser and inspect the certificate's validity dates directly. The new expiry date should be well in the future and the warning should clear.