How to fix: Certificate is not yet valid
The certificate the server presents has a notBefore date later than the time of the scan, so it has not started being valid.
Why it matters
Every client with a correct clock rejects the connection with a certificate validity error, so HTTPS is effectively down for them. Worse than the outage is the habit it builds: users who are told to click through the interstitial learn to ignore exactly the warning that would otherwise stop a real interception.
This is usually a clock problem rather than a certificate problem. Either the issuing system's clock ran ahead when the certificate was signed, or the server's own clock is behind and a perfectly valid certificate looks premature. Comparing the server's time against NTP is the first thing to check, because reissuing will not help if the clock is the cause.
How to fix it
- 1Check the server's system clock and confirm NTP is running and synchronised.
- 2If the clock is correct, reissue: the certificate's notBefore really was set in the future.
- 3Where a certificate is deliberately pre-issued for a future cutover, do not deploy it until its notBefore has passed.
Code examples
Compare certificate dates against the clock
date -u
openssl s_client -connect example.com:443 </dev/null 2>/dev/null \
| openssl x509 -noout -datesConfirm time sync
timedatectl status
chronyc tracking 2>/dev/null || ntpq -pReferences
Detected automatically by VulnRadar. The check id is tls-cert-not-yet-valid, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is Certificate is not yet valid?
- VulnRadar rates this high severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id tls-cert-not-yet-valid, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Certificate is not yet valid map to?
- It maps to CWE-298. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.