How to fix: Server Date header shows clock skew
The Date response header shows a time significantly different from the current time, indicating a misconfigured server clock.
Why it matters
Severe clock skew can cause authentication token expiration issues, TOTP/HOTP MFA code rejection, TLS certificate validation failures, and session management problems. Predictable skew can also help attackers infer server restart times or virtualization artifacts.
Ensure NTP synchronization is configured and running on all servers.
How to fix it
- 1Enable and configure NTP: systemctl enable --now systemd-timesyncd
- 2Verify time sync: timedatectl status
- 3For containers, ensure the host clock is synchronized and the container inherits it
Code examples
Linux: enable NTP sync
# Enable systemd-timesyncd
systemctl enable --now systemd-timesyncd
# Check sync status
timedatectl show --property=NTPSynchronized
# Or install and configure chrony for better accuracy:
apt-get install chrony
service chrony restartReferences
Detected automatically by VulnRadar. The check id is date-time-skew, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Server Date header shows clock skew?
- VulnRadar rates this info severity in the headers 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 date-time-skew, which stays the same between runs so you can filter, diff, or gate CI on it.
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.