Browser policy enforcement
Content-Security-Policy can restrict where scripts, styles, frames, images, connections, and other resources may come from. Frame controls can also limit where a page may be embedded.
HTTP security response headers let a server ask the browser to enforce additional rules around resource loading, HTTPS, MIME handling, referrer information, framing, and selected browser features. Used well, they can reduce exposure to problems such as cross-site scripting, clickjacking, MIME confusion, and unnecessary information leakage.
Presence alone is not enough. A Content-Security-Policy can exist while remaining overly permissive, HSTS can be returned with a very short lifetime, and some headers are optional or depend on how the website actually works. A useful report examines both the header and its value. The scanner explains the observed settings, and the Knowledge Base provides configuration guidance.
Core concepts
Security headers do different jobs. It is more useful to understand the job of each group than to treat every header as another checkbox.
Content-Security-Policy can restrict where scripts, styles, frames, images, connections, and other resources may come from. Frame controls can also limit where a page may be embedded.
HSTS tells supporting browsers to keep using HTTPS for a defined period, while X-Content-Type-Options helps stop browsers from interpreting certain resources as a different MIME type than the server declared.
Referrer-Policy controls how much referrer information leaves the page. Permissions-Policy can restrict selected browser features such as camera, microphone, geolocation, and other capabilities where supported.
Key headers
These are common signals in a security-header report, but their usefulness still depends on configuration and website requirements.
Defines which sources and behaviors the browser should allow for different types of content. A carefully designed policy can substantially reduce the impact of injected content.
Tells browsers that have reached the site securely to continue using HTTPS for the specified max-age. The policy can optionally include subdomains.
The nosniff value prevents MIME sniffing and blocks scripts or styles served with unsuitable types. Correct Content-Type values remain essential.
Controls how much information from the current URL is included in the Referer header when the browser follows links or loads resources.
If you would like to read more about Security Headers, check out the Knowledge Base for detailed header references, configuration guidance, common problems, and server-specific examples.
Browse Knowledge BaseCopyright ©2026 MILAN INNOVATIONS LLC. All rights reserved.