Security Headers Builder and Checker

Inspect supplied security headers or draft bounded Nginx and Apache configuration.

On-device No sign-up Free to use

Build or check headers controls

Showing an example. Edit to see your own.

Drop your file here

or choose one from your device

Replaces pasted headers in Check or Inspect mode. Up to 100,000 bytes. In DevTools, choose Network, select a request, then copy its response headers.

    ?

    Used by Check and Inspect. Inspect groups caching, content, security and cookies; credential values are hidden in its report. The tool does not fetch a URL.

    ?

    One Name: value per line, for anything the choices above do not cover. Content-Security-Policy is refused here because the CSP Generator page builds it.

    What to do
    ?

    Check evaluates supported security headers in supplied response text. Inspect groups pasted request/response headers. Build drafts headers from the choices below.

    ?

    The presets start at 180 days and do not offer a short trial duration. Check HTTPS support for the host and any affected subdomains before applying a cached HSTS rule.

    ?

    Adds the preload declaration, not an automatic list enrollment. Inclusion has additional requirements and a separate submission; removal can take months.

    ?

    0 turns off the legacy XSS filter, which current guidance recommends.

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    Draft the default eight headers with one-year HSTS, includeSubDomains and no preload request.

    Wrote 8 headers. Content-Security-Policy is not included; build it on the CSP Generator page.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/security-headers-builder-checker · 20 November 2026

    Was this helpful?

    How to use Security Headers Builder and Checker

    1. Choose Check pasted headers for the supported security-header checks, Inspect any pasted headers for grouped explanations, or Build a header block for a draft.
    2. For Check or Inspect, paste a captured header block or select its UTF-8 file. The file takes priority. Browser DevTools can provide the response headers for a specific request.
    3. For Build, choose the required HSTS, framing, referrer, feature and cross-origin settings. Read the effects before copying; the controls do not test your application.
    4. Review the updated findings or draft and its Nginx/Apache snippets. Test a draft in the intended application context, and verify the actual response separately.

    Example: Security Headers Builder and Checker

    Draft the default eight headers with one-year HSTS, includeSubDomains and no preload request.

    You add
    What to do: build; Request or response headers: HTTP/2 200 strict-transport-security: max-age=31536000; includeSubDomains x-content-type-options: nosniff x-frame-options: SAMEORIGIN referrer-policy: strict-origin-when-cross-origin content-type: text/html; charset=utf-8 server: nginx; HSTS max-age: 31536000; Include subdomains: true; Ask for preload: false; X-Frame-Options: SAMEORIGIN; Send X-Content-Type-Options: nosniff: true; Referrer-Policy: strict-origin-when-cross-origin; Permissions-Policy: geolocation=(), camera=(), microphone=(); Cross-Origin-Opener-Policy: same-origin; Cross-Origin-Resource-Policy: same-origin; Send X-XSS-Protection: 0: true
    You get
    Wrote 8 headers. Content-Security-Policy is not included; build it on the CSP Generator page.

    Options

    What to do
    Check evaluates the supported security headers in pasted response text. Inspect groups supported request/response headers and masks credential values. Build drafts headers from the choices below.
    Local UTF-8 header file (optional)
    Replaces pasted headers in Check or Inspect mode. Up to 100,000 bytes. In DevTools, choose Network, select a request, then copy its response headers.
    Request or response headers
    Used by Check and Inspect. Inspect groups caching, content, security and cookies; credential values are hidden in its report. The tool does not fetch a URL.
    HSTS max-age
    The presets offer omission or 180 days, one year and two years, not a short trial duration. A learned HSTS rule is cached. Check HTTPS support for the intended host and, with includeSubDomains, every affected subdomain.
    Include subdomains
    Adds includeSubDomains to the HSTS draft when HSTS is enabled. Review every affected subdomain before using that header.
    Ask for preload
    Adds the preload declaration to the HSTS draft, requiring includeSubDomains and at least one year. This does not submit the domain or enroll it automatically. List inclusion has additional requirements; removal can take months.
    X-Frame-Options
    Choose SAMEORIGIN, this site may frame it, DENY, no page may frame it, Do not send it.
    Send X-Content-Type-Options: nosniff
    Adds the nosniff response header to the draft. The generator does not check the content types your server actually sends.
    Referrer-Policy
    Choose no-referrer, strict-origin-when-cross-origin, same-origin, origin-when-cross-origin, no-referrer-when-downgrade, unsafe-url.
    Permissions-Policy
    Choose Turn off location, camera and microphone, Those three plus payment, Do not send Permissions-Policy.
    Cross-Origin-Opener-Policy
    Sets the opener policy for cross-origin windows and browsing-context groups. This can affect popup workflows; test the actual application before applying a draft.
    Cross-Origin-Resource-Policy
    Sets which origins/sites may use this response for applicable no-cors resource requests. It is distinct from CORS response-reading permission and can affect embedded resources.
    Send X-XSS-Protection: 0
    0 turns off the legacy XSS filter, which current guidance recommends.
    Extra headers (optional)
    One Name: value per line, for anything the choices above do not cover. Content-Security-Policy is refused here because the CSP Generator page builds it.

    Supported inputs and limits

    • The default draft contains eight headers; omitted choices and extra lines change that count.
    • CSP is handled by the separate CSP Generator.
    • Check/Inspect accept up to 100,000 characters and 200 fields; an optional UTF-8 file is capped at 100,000 bytes.
    • General inspection stops at the first blank line after headers, refuses folded/control-bearing lines and caps values at 4,096 characters.
    • Unknown fields are listed without guessed explanations.
    More details

    Results cover supplied text only, not a live URL, cached HSTS state, effective browser policy or a security grade.

    Server snippets are drafts and no server is changed.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Keep HSTS learning separate from preload enrollment

    A browser can learn an HSTS rule from an HTTPS response or already have a cached, inherited or preloaded rule. Adding preload to a draft is a declaration, not a submission or a completed browser-list update. Review the preload service’s current requirements and long-term subdomain consequences separately. The default here leaves that option off.

    Read the different cross-origin controls separately

    Cross-Origin-Opener-Policy concerns window relationships and browsing-context groups. Cross-Origin-Resource-Policy controls applicable no-cors resource use; it does not grant scripts permission to read cross-origin responses. CORS handles that separate response-sharing question. Likewise, nosniff works with the declared Content-Type, including script/style MIME checks. None of these drafts confirms the types, windows or resources your application actually uses.

    Questions about Security Headers Builder and Checker

    Where do I get the response headers?

    Run a header request such as curl -I against the address, or open the Network panel in your browser's developer tools, select the document request and read its response headers. Copy the whole block, including the status line, because the page skips it for you.

    Why is Content-Security-Policy not built here?

    A policy has to allow exactly the sources your page uses, and a wrong one either breaks the page or allows more than intended. That needs its own page with its own checks, and this site has one, so this tool stays with the headers that take a single value.

    Can I trust a check of pasted headers for my live site?

    Only for the response you pasted. A CDN, a proxy or an application framework can add or remove headers on the way to the browser, and a cached response can come from a layer that behaves differently from the origin. Request the address you actually serve, from the same path a visitor takes, and compare more than one response when a layer sits in front.

    Is HSTS safe to turn on?

    Use HSTS only for a host that can continue serving HTTPS, and cover subdomains only when they can too. Browsers cache learned rules; omitting the header later does not erase them. The presets here start at 180 days, so they are not a short trial. Preload is a separate, longer-lived list commitment and is not enabled automatically by this tool.

    What does to review mean?

    It marks a value that is present but not the one this page expects, such as a short max-age, a legacy X-XSS-Protection value, or a name that was renamed. It is a prompt to read the value, not an automatic failure, because your hosting may have a reason for it.

    Page updated · Project managed by Tony Hines · Report a problem with Security Headers Builder and Checker