← Back to help centre

Security and TLS

Security-header monitoring

Understand missing required headers, saved baselines and security-header weakening warnings.

WebCheck can inspect common HTTP security headers on a monitored page. This is a configuration check, separate from whether the page is reachable.

Headers recorded

The check records the response values for Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy. The current target setup requires CSP and HSTS by default. Presence is not a security review: WebCheck does not decide whether a policy's contents are strong or appropriate for your application.

Missing and weakened headers

A configured required header that is absent produces a security_header_missing result. On the first successful security-header evaluation, WebCheck saves the observed header set as a baseline and records when it was captured. If a header that was present in that baseline later disappears, WebCheck reports security_header_weakened and shows the missing header in the run evidence.

Edit the target to see the baseline time or explicitly capture a fresh header baseline after an intentional configuration change. The replacement is taken on the next successful security-header check; it does not dismiss or fabricate an outage. Older baselines may not have a recorded capture time and can be replaced with a dated snapshot.

A header warning does not mean the HTTP endpoint is down. It is a separate security/configuration signal and is not counted as HTTP/TCP availability. It can still open an incident for the security-header check after that check's configured failure threshold.

Investigate a warning

Compare the current response headers with the run evidence and your proxy/CDN and application configuration. If the change was intentional, review the requirement before changing the check; do not assume that a missing header is harmless. If a deployment or routing change removed a header unexpectedly, restore it at the layer that owns the response.

See also TLS and certificates, DNS monitoring and Understanding check history.