How to fix: Expect-CT Header Not Present
The Expect-CT header is absent. This is informational, not something to fix: Chrome deprecated and removed Expect-CT support, and Certificate Transparency is now enforced unconditionally by browsers at certificate-validation time, independent of any response header. Essentially no site, including well-secured ones, sends this header anymore.
Why it matters
None from the header's absence specifically. CT enforcement no longer depends on it, so not sending Expect-CT does not weaken CT protection in any current browser.
Expect-CT let a site opt into CT enforcement and violation reporting before browsers enforced CT by default. Chrome has required CT for all publicly trusted certificates since 2018 and has since removed Expect-CT support entirely (MDN marks it deprecated, not for use in new sites). This finding is kept at info purely for completeness; there is no meaningful action to take.
How to fix it
- 1No action needed. Expect-CT is deprecated and no longer enforced by any major browser.
- 2Rely on your CA's CT log submission (automatic for all publicly trusted CAs) instead.
Code examples
No header needed
# Expect-CT is deprecated (removed from Chrome). CT is enforced automatically
# via your CA's log submission during certificate issuance -- nothing to configure.References
Detected automatically by VulnRadar. The check id is expect-ct-missing, stable across every scan so you can filter or diff on it.
More ssl checks
- HighSecure Cookie Set on HTTP Endpoint
- CriticalSite Served Over Unencrypted HTTP
- LowHTTPS Served on Non-Standard Port
- InfoX-HTTP-Method-Override / X-Forwarded-Method Header in Response
- InfoHSTS Present on HTTP Response (SSL-Strip Indicator)
- MediumMixed-Protocol Content (HTTPS Page Loading HTTP Resources)
- LowHSTS declared in a meta tag, where browsers ignore it
- MediumAlt-Svc advertises cleartext HTTP/2 (h2c)
Questions
- How severe is Expect-CT Header Not Present?
- VulnRadar rates this info severity in the ssl 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 expect-ct-missing, 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.