WordPress SSL Certificate Expired? Causes, Fixes and Monitoring

An expired SSL certificate is one of the most visible failures a site can have: visitors see a full-page security warning instead of your website. Monitoring is the part of website care that catches it — along with outages — before it matters. A service checks your site around the clock, and the moment something looks wrong, it sends an alert. But an alert is only the start — what happens after the ping is what makes monitoring useful.

What automated monitoring checks

Our plans include two continuous checks:

• Availability — the site is requested at regular intervals, and a failure to respond, or an error response, is flagged.
• SSL certificate expiry — the certificate that keeps your site on HTTPS is checked, with a warning well before it expires.

These are deliberately simple signals. They answer “is the site reachable?” and “will visitors soon see a security warning?” — two questions worth knowing about quickly.

What an alert does — and doesn’t — mean

A single failed check isn’t always an outage. A brief network hiccup, a slow response during a traffic spike or a problem in one region can all trigger a warning. That is why the first step is always to confirm: is the site really down, for whom, and since when?

What happens after the ping

1. Confirm the problem is real and see what visitors are experiencing.
2. Find where it sits: the site itself, the hosting server, DNS, or a third-party service.
3. Act or escalate: fix what is within reach, or contact the host or provider with the evidence.
4. Explain what happened and what, if anything, needs a decision from you.

Monitoring runs continuously, but human response follows the working hours and arrangements agreed before your plan starts. We are open about that: a care plan is not a round-the-clock emergency desk, and it is better to know the response times upfront than to assume them.

Why SSL certificates still expire

Most hosts now issue free certificates that renew automatically, which is great — until renewal quietly fails. Common reasons include DNS changes that point the domain elsewhere, a proxy or CDN in front of the site, or a hosting change that left the old renewal behind. Because certificates are short-lived by design, a failed renewal can turn into a browser warning within weeks. An expiry alert catches it while there is still time to fix it calmly.

How to fix an expired certificate

1. Check where the certificate comes from. Most WordPress sites get it from the host; some from a CDN or proxy in front of the site. WordPress itself doesn’t issue certificates.
2. Reissue or renew it in the hosting control panel (or the CDN’s dashboard).
3. If renewal fails, check DNS. The domain must point to the host that issues the certificate.
4. Clear caches and test the site in a private browser window.
5. Check for mixed content — images or scripts still loading over HTTP — if the site was recently moved to HTTPS.

What sits outside anyone’s control

Some outages start elsewhere: a hosting provider’s incident, a DNS provider, or an external service the site relies on. Monitoring still helps here — it tells you quickly, and it gives the evidence needed to chase the right provider — but the fix may not be in our hands or yours.

What you can do

• Keep your domain on auto-renew, with a payment method that won’t expire unnoticed.
• Tell us before changing DNS, hosting or adding a CDN.
• Make sure we know who to contact if the site is down outside office hours.

Frequently asked questions