The certificate the site sent is outside its dates — expired, or not valid yet — as far as the device’s clock can tell. Most often the certificate really has expired because automatic renewal quietly failed; sometimes the visitor’s clock is wrong.
Your connection is not private Attackers might be trying to steal your information from example.com (for example, passwords, messages, or credit cards). NET::ERR_CERT_DATE_INVALID
How 8 other clients word the same error
Firefox
Error code: SEC_ERROR_EXPIRED_CERTIFICATE — “Firefox doesn’t trust this site because it looks like the certificate expired on …”
curl (OpenSSL)
curl: (60) SSL certificate problem: certificate has expired
curl 8.17 and later (OpenSSL)
curl: (60) SSL certificate OpenSSL verify result: certificate has expired (10)
curl on Windows (Schannel)
curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_CERT_EXPIRED (0x80090328) - The received certificate has expired.
Python
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1028)
Node.js
Error: certificate has expired — code: CERT_HAS_EXPIRED
Go
x509: certificate has expired or is not yet valid: current time … is after …
WordPress
cURL error 60: SSL certificate problem: certificate has expired
| Error | NET::ERR_CERT_DATE_INVALID |
| Usually fixed by | The website |
| Firefox | SEC_ERROR_EXPIRED_CERTIFICATE, MOZILLA_PKIX_ERROR_NOT_YET_VALID_CERTIFICATE |
| OpenSSL | certificate has expired (10), certificate is not yet valid (9) |
| Can visitors click through? | Yes, unless the site uses HSTS |
Check the certificate a site serves
Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.
What it means
Every certificate is valid between two dates, notBefore and notAfter. Browsers compare them with the device’s clock; outside that window the certificate is refused, because an expired certificate — or one used before its time — could be an old or stolen one. Chrome’s own notes name three causes: a misconfigured server, an attacker using an old certificate, or a wrong clock.
When a certificate has several problems, Chrome shows the most serious: an expired certificate that is also untrusted shows NET::ERR_CERT_AUTHORITY_INVALID instead.
Why it happens
- Automatic renewal failed — Let’s Encrypt, cPanel AutoSSL or the host’s renewal stopped working, and nobody was told: Let’s Encrypt stopped sending expiry emails in June 2025.
- The certificate was renewed but not installed everywhere: another server, a load balancer or the CDN still serves the old one.
- The server was not reloaded after renewal.
- On the visitor’s side, a device clock set wrong — see “Your clock is behind”.
How to fix it
- Run the check above to see the dates of the certificate the site actually serves.
- Renew the certificate. For Let’s Encrypt, run the client’s renew command and read why the last automatic run failed — usually port 80 blocked for validation, a changed DNS record or a CAA record.
- Install it on every server, load balancer and CDN that serves the name, with its full chain, and reload the web server.
- Set up monitoring so the next expiry does not surprise you — lifetimes are getting shorter: 200 days at most since March 2026, and Let’s Encrypt is moving to 45 days.
If you are visiting the site
- Check the device’s date, time and time zone. If they are right, the site’s certificate has expired and only the site can fix it.
See it for yourself
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -dates
Prints the notBefore and notAfter dates of the certificate the server sends. Add -checkend 2592000 to ask whether it expires within 30 days.
Questions
My certificate was renewed — why do visitors still see it expired?
Because a server still sends the old one: the web server was not reloaded, or another server, load balancer or CDN has its own copy. The check above shows exactly which certificate the site serves.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- net/base/net_error_list.h — chromium.googlesource.com
- What does “Your connection is not secure” mean? — support.mozilla.org
- X509_STORE_CTX_get_error — docs.openssl.org
- curl — SSL CA Certificates — curl.se
- Expiration Notification Service Has Ended — letsencrypt.org