Certificate Expired on a Trusted Site? Fix It Fast

1. Your Computer's Date and Time Is Wrong

This is the number one cause of the "certificate expired" error on a site you know is safe. Your browser checks the certificate's valid-from and valid-to dates against your system clock. If your clock is even a few hours off—say, set to 2022 or 2026—the browser thinks the certificate is expired or not yet valid.

I've seen this happen after a dead CMOS battery, a time zone change during travel, or Windows Time service glitching after a sleep/wake cycle. The fix is quick.

How to Fix It on Windows 10 or 11

1. Right-click the clock in the bottom-right corner of your taskbar and pick Adjust date/time.
2. Turn on Set time automatically. If it's already on, flip it off, wait 5 seconds, then flip it back on. After you do this, you should see the clock jump to the correct time within a few seconds.
3. Turn on Set time zone automatically too. This matters more than you'd think—a wrong time zone shifts the time by hours.
4. Scroll down and click Sync now under "Additional settings." You'll see a message saying "Sync in progress..." then "Your clock was successfully synchronized."
5. Now restart your browser and try the site again. If the error goes away, you're done. If not, move on to fix #2.

On a Mac: Open System Settings > General > Date & Time. Turn on Set time and date automatically. Pick "time.apple.com" from the dropdown. Then restart Safari or Chrome.

For Android or iOS: Go to Settings > General management > Date and time (Android) or Settings > General > Date & Time (iPhone). Turn on Automatic date & time. Done.

2. Browser SSL Cache Is Stale

Your browser keeps a cache of SSL certificates it's seen before. Sometimes that cache gets corrupted or holds an old version of a certificate that's been renewed. On a site you visit daily—like Google, Facebook, or your bank—the cached cert might be the old one, while the site already switched to a new certificate. The browser sees the mismatch and throws the expired error.

This is especially common in Chrome and Edge, which are both Chromium-based. I've seen it after a site's certificate was reissued due to a security breach or a simple renewal.

Clear the SSL Cache in Chrome, Edge, or Brave

1. Open your browser and type chrome://net-internals/#hsts (if using Chrome, Edge, or Brave) into the address bar. Press Enter.
2. Scroll down to the Delete domain security policies section.
3. Type the domain name of the site that gave you the error (for example, google.com or yourbank.com). Then click Delete. You'll see a confirmation: "Deleted example.com security policies."
4. Next, open a new tab and go to chrome://settings/clearBrowserData.
5. Set the time range to All time.
6. Check only Cached images and files. Uncheck everything else unless you want to lose passwords and cookies.
7. Click Clear data. You'll see a loading spinner for a few seconds.
8. Restart the browser completely. Then visit the site again.

For Firefox: Go to Options > Privacy & Security > Cookies and Site Data > Clear Data. Check only Cached Web Content. Click Clear. Then restart Firefox.

If the error persists, your browser might have a deeper cache. On Windows, you can clear the entire certificate store, but that's overkill. The fix above works 90% of the time for cache issues.

3. The Site's Certificate Is Actually Expired or Misconfigured

Sometimes the problem isn't you—it's the website. I've run into this on small business sites, school portals, and even government pages that forgot to renew their SSL certificate. It happens. The certificate expires, the webmaster doesn't notice, and you get the error.

Here's how to check if it's the site's fault.

Verify the Certificate Manually

1. In the browser that shows the error, look for a padlock icon or a "Not Secure" warning in the address bar.
2. Click the padlock (or the warning) and select Connection is secure > Certificate is valid (or similar wording depending on browser).
3. A window pops up showing the certificate details. Check the Validity section. Look at the Valid from and Valid to dates. If the current date is outside that range, the certificate is genuinely expired.
4. If the dates look correct but it still throws an error, the certificate might be for the wrong domain (a mismatch). Look at the Subject field—it should match the site's URL. If it says *.example.com but you're on example.org, that's a mismatch.

What to do: If the certificate is expired or mismatched, you can't fix it from your end. You have two choices: visit the site anyway (click "Advanced" or "Proceed" in the warning) if you trust it, or contact the site owner. For a bank or email provider, don't proceed—call them. For a blog or forum, you can safely click through if you understand the risk (your data isn't encrypted between you and the server).

One more thing: sometimes a CDN or reverse proxy (like Cloudflare or AWS CloudFront) misconfigures the certificate. That's rare but happens. If the site works in one browser but not another, that points to a cache issue, not a real expiration.

Quick-Reference Summary Table

Try them in that order. You'll fix the problem before you even finish your coffee.