Loading...

HTTP Security Header Checker

Inspect security headers, understand missing protections and review configuration warnings.

HTTP/HTTPS · ports 80/443 · up to 3 redirects · no API key. URLs are sent to the server; avoid links containing secrets.

Fetching response headers and checking policies…

Review the headers protecting your pages

A snapshot of the final response, not a full security audit. CSP and application-specific policies need manual review. Checks target web pages; some protections do not apply to JSON, images or other resources.

0
Basic check passed
0
Needs review
0
Missing
0
Information

Check results

The final response is not a successful 2xx response. These findings may describe an error, challenge or redirect page.

A snapshot of the final response, not a full security audit. CSP and application-specific policies need manual review. Checks target web pages; some protections do not apply to JSON, images or other resources.

Security header analysis

Request path

    Final response headers

    Repeated fields are preserved. Set-Cookie and authentication-info values are hidden in both the report and exports.

    HeaderValue

    Follow VuiZ.Net on Google Search

    Add VuiZ.Net as a preferred source on Google to find your favorite tools more easily.

    • Find your tools again
    • Discover new utilities
    • Support VuiZ.Net
    Follow

    Understand the security headers returned by a web page

    Enter a public HTTP or HTTPS address to inspect its response headers. VuiZ sends a GET request from the server, follows up to three redirects and analyzes the final response. No API key is needed.

    The report separates basic checks that pass, missing headers, warnings and context-dependent information. It does not assign a website security grade: an enforced CSP, for example, still needs review against the application and its resources.

    Key features

    • Header values and explanations Review HTTPS, HSTS, CSP, framing controls, nosniff, Referrer-Policy, Permissions-Policy, COOP, COEP, CORP, the legacy XSS filter and server information disclosure.
    • Trace the response See the requested and final URL, status code and redirect chain. Repeated response headers remain separate so conflicting values are visible.
    • Portable report Filter warnings and missing headers, then copy or download the full JSON report. Cookie values and authentication-info fields are redacted before the report is returned.

    Check a website’s HTTP security headers

    Inspect one public page and review the findings in context.

    1. Enter a public page URL Paste an HTTP or HTTPS URL. If you omit the scheme, HTTPS is used. Only ports 80 and 443 are accepted.
    2. Run the check Select Check headers and wait for the server to retrieve the response headers.
    3. Review findings and redirects Confirm the final URL and status code, then use Needs attention to focus on missing or suspicious headers. Read the recommendation for each check.
    4. Export or check another page Copy or download JSON to keep the report, or select Reset before checking another URL.

    Usage tips

    • Check the actual HTML page as well as other important routes. CDN, login, API and error responses can use different policies.
    • A CSP recommendation is a review prompt, not a ready-to-paste policy. Test changes with your application before enforcing them.
    • The server receives the URL, including its query string. Avoid submitting private links or secrets. The tool does not store reports or send your browser cookies to the target.

    Frequently asked questions

    This tool evaluates security-related response headers and explains the findings. The general HTTP Header Checker focuses on inspecting HTTP requests and response values.
    No. Checks cover observable headers from one server-side request. They do not test application vulnerabilities, authenticated pages, HTML meta policies or every CSP source and browser behavior.
    CSP validity and effectiveness depend on its sources, nonces, hashes and the application. The tool flags common concerns, distinguishes report-only from enforced policies and leaves a full policy review to you.
    Permissions-Policy and cross-origin isolation settings depend on the application. X-XSS-Protection is obsolete and its absence is not treated as a failure. A restrictive CSP frame-ancestors policy can replace X-Frame-Options.
    Private addresses, invalid TLS certificates, HTTPS-to-HTTP redirects and excessive responses are rejected. WAFs, geography, authentication and user agents can change the response. The tool makes at most four requests, with a 15-second network budget; system DNS resolution can take longer.