Expect-CT (Expect-CT)
Why Expect-CT Is Important
Expect-CT was useful during the transition period when Certificate Transparency was not universally required. It allowed early adopters to enforce CT on their domains before browsers mandated it globally. With Chrome and other browsers now requiring CT for all new certificates, the header is no longer needed.
If your server still sends Expect-CT, it is harmless but unnecessary. Modern browsers ignore it. You can safely remove it to reduce header size. The underlying protection - requiring CT compliance - is now built into browser certificate validation.
The report-uri feature of Expect-CT allowed site operators to receive notifications about CT compliance failures. This reporting capability is still useful but is now better served by Certificate Transparency monitoring services that watch CT logs directly.
How to Check
A security audit may still check for Expect-CT. If present, it can be safely removed since all browsers now enforce CT by default. Focus on monitoring CT logs (via crt.sh or similar services) for unauthorized certificate issuance.