# A post-deploy security-header check that does not stop at the status code

I build BugSweep, a website configuration-monitoring tool. This draft was prepared with AI assistance and requires my technical review before publication.

A successful HTTP response answers one question: did this request receive a response? It does not tell you whether a deployment preserved your security headers.

Start with a baseline from a site you own or are authorized to maintain. Record the public URL, redirect destination and response headers after you have reviewed the configuration. Repeat the same check after changes to the application, reverse proxy or CDN. Keep the hostname, path and request method consistent so you are comparing like with like.

Review differences rather than counting header names. A header can remain present while its policy changes. Content-Security-Policy deserves particular care: a restrictive policy can break scripts or other resources that the application needs. Content-Security-Policy-Report-Only lets browsers report violations without enforcing that policy. Use it to understand the site's behavior before moving to an enforcing policy; do not copy a strict example into production and assume it is compatible.

HSTS has different consequences. Strict-Transport-Security tells browsers to remember that a host should use HTTPS. A previously learned policy can remain in the browser until its lifetime expires, so removing the header is not an instant reset for existing visitors. Review the max-age and any includeSubDomains directive deliberately. Subdomains may have different owners or HTTPS readiness, and a setting that is appropriate for the main site is not automatically appropriate for all of them.

When a baseline changes, write down three things: what changed, whether it was intended, and who owns the decision. Preserve the response evidence with the time and URL. A useful alert identifies the configuration change; it should not declare an exploit or a breach from a missing header alone.

Headers are one layer. This checklist does not test application authorization, dependencies, backups or the server's complete security. Use it as a small, repeatable part of a wider website-care process.

References:

- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy-Report-Only
