Instantly check whether your site sends the security headers that matter most — CSP, HSTS, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. Free, no signup.
Free plan · 1 URL check at a timeThese 5 headers are a great baseline. Pair this with our SSL Checker to also confirm your certificate and TLS configuration are solid.
Run Free Website AuditHTTP security headers are instructions your server sends to every visitor's browser, telling it how to behave defensively — what content is allowed to load, whether the connection must stay encrypted, whether the page can be embedded in another site, and more. They cost nothing to add and take effect instantly, yet a huge share of sites still ship with most of them missing. This tool sends one live request to your URL, reads the actual response headers your server returns (following redirects to the final page), and evaluates five of the most widely recommended headers: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. Each is scored on whether it's present and reasonably configured, rolled into a single 0–100 score, with the full raw header dump shown so you can verify exactly what we saw.
This is a deliberately focused baseline check, not a full security audit. It doesn't cover every possible header (such as Permissions-Policy or cookie security flags), and it doesn't evaluate your TLS/SSL certificate or encryption configuration — for that, pair this tool with our SSL Checker. Header requirements can also vary by site: a header that's essential for one type of site (like a strict CSP on a page with lots of third-party embeds) may need tuning rather than a blanket "on." Treat this as a fast way to catch obvious gaps, not a compliance certification.
Website security involves more than installing an SSL certificate or using HTTPS. Your server also needs to communicate security instructions to visitors' browsers, explaining how certain types of content should be handled and which browser behaviours should be restricted.
These instructions are commonly delivered through HTTP security headers. They help protect websites and visitors against several browser-based security risks, including cross-site scripting (XSS), clickjacking, content-type confusion, and accidental exposure of sensitive browsing information.
For example, a website can use a Content-Security-Policy header to control which sources are permitted to load scripts, stylesheets, images, and other resources. Strict-Transport-Security can instruct compatible browsers to use HTTPS for future connections, while X-Frame-Options can help prevent a page from being embedded in another website.
Although security headers do not replace secure coding, server configuration, or regular vulnerability testing, they provide an important layer of browser-side protection. They are also often overlooked during website development and maintenance.
The Auditest HTTP Security Headers Checker helps website owners, developers, SEO professionals, and administrators identify missing or potentially misconfigured security headers. It sends a live request to the URL you provide, follows redirects to the final destination, and examines the actual HTTP response headers returned by the server.
Rather than relying on a generic checklist, the tool evaluates five widely recommended security headers, provides an overall score from 0 to 100, and displays the raw response headers so you can inspect the results.
Browsers do not automatically know every security rule a website owner wants to enforce. HTTP security headers provide additional instructions that help browsers handle website content more safely.
When important headers are missing, a website may lack useful protections against certain attacks. For example, without appropriate framing restrictions, an attacker may be able to embed a page in another website and attempt a clickjacking attack.
Similarly, a poorly configured Content-Security-Policy may leave unnecessary content sources permitted, increasing exposure to certain script-injection risks.
Implementing suitable headers can help you:
Reduce exposure to selected browser-based attacks.
Control which external sources are permitted to load website resources.
Help prevent unauthorised framing of sensitive pages.
Reduce certain content-type confusion risks.
Encourage HTTPS connections through supported browser policies.
Control how much referring-page information is shared with other websites.
Identify weaknesses in your server's HTTP response configuration.
The important point is that security headers should be configured according to your website's architecture and requirements. Adding a header without understanding its effect can cause problems, such as blocking legitimate scripts, breaking embedded content, or preventing access to resources.

The Auditest checker focuses on five important HTTP security headers. Each serves a different purpose, and its configuration should be considered in the context of the website.
Content-Security-Policy is a browser security mechanism that allows website administrators to define which sources are permitted to provide content to a page.
It can control resources such as JavaScript, CSS, images, fonts, frames, and other content. A carefully configured CSP can reduce the impact of certain cross-site scripting and content-injection attacks.
For example, a policy can restrict scripts to approved sources rather than allowing scripts from arbitrary external locations.
However, CSP requires careful implementation. A policy that is too restrictive may break legitimate website functionality, while an overly permissive policy may provide limited protection.
What to check: Whether a Content-Security-Policy header is present and whether its configuration provides meaningful restrictions for the website.
Strict-Transport-Security tells supported browsers to access a website using HTTPS for a specified period.
Once a browser accepts a valid HSTS policy, it can automatically upgrade future HTTP attempts to HTTPS, helping reduce the risk of certain protocol downgrade and interception attacks.
An HSTS header commonly includes a max-age directive, which specifies how long the browser should remember the HTTPS requirement.
Some websites also use includeSubDomains and preload, but these directives require careful consideration. Applying HSTS to subdomains that do not support HTTPS can make them inaccessible through normal browser connections.
What to check: Whether the header is present and whether its policy contains a meaningful duration and appropriate directives.
X-Frame-Options helps control whether a browser can display a webpage inside a frame or iframe on another website.
This is useful for reducing the risk of clickjacking, where an attacker places a legitimate website interface inside a hidden or misleading frame to trick visitors into clicking something they did not intend to click.
Common values include:
DENY – Prevents the page from being displayed in frames.
SAMEORIGIN – Allows framing only by pages from the same origin.
The appropriate setting depends on whether your website legitimately needs to be embedded elsewhere. Modern websites can also use the frame-ancestors directive in Content-Security-Policy for more flexible framing control.
What to check: Whether the response includes a suitable framing restriction.
X-Content-Type-Options helps prevent browsers from interpreting files as a different content type from the one declared by the server.
Its commonly used value is:
nosniff
This instructs supported browsers not to perform certain MIME-type sniffing behaviours. It is particularly relevant when serving scripts and stylesheets because incorrect content-type handling can create security risks.
For this header to work effectively, your server must also send appropriate Content-Type values for the resources it serves.
What to check: Whether the header is present with the expected nosniff value.
Referrer-Policy controls how much information a browser includes in the Referer header when a visitor follows a link or loads a resource from another location.
Depending on the policy, a browser may share the full referring URL, only the website origin, or no referrer information.
This matters because URLs can sometimes contain sensitive information, such as internal paths or tracking parameters. A suitable policy helps website owners manage how much browsing information is shared with external destinations.
Common policies include:
no-referrer – Sends no referrer information.
same-origin – Sends referrer information only for same-origin requests.
strict-origin-when-cross-origin – Generally sends the full URL for same-origin requests and only the origin for cross-origin HTTPS requests.
What to check: Whether a Referrer-Policy header is present and whether its value suits the website's privacy requirements.

The checker is designed to provide a practical assessment using the actual HTTP response from your website.
Follow these steps:
Enter your website URL: Provide the full address of the page or website you want to test, including its protocol, such as https://example.com.
Start the security headers check: The tool sends a live HTTP request to the submitted URL.
Follow redirects: If the submitted address redirects to another destination, the checker follows the redirect and examines the final page's response.
Read the response headers: The tool retrieves the HTTP headers returned by the server.
Evaluate five security headers: It checks Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
Review the security score: The results are combined into an overall score between 0 and 100.
Inspect the raw headers: You can examine the full raw header output to verify what the server actually returned.
This approach helps you identify missing security instructions without manually inspecting browser developer tools or running complicated command-line requests.
The checker provides an overall score from 0 to 100 based on its evaluation of the five supported headers.
A higher score generally indicates that more of the checked headers are present and reasonably configured according to the tool's assessment. A lower score suggests that one or more recommended headers may be missing or need attention.
However, the score should be interpreted carefully. It is a summary of a limited set of checks, not a universal measure of website security.
For example, a website could receive a high score while still having vulnerabilities in its application code, outdated software, insecure authentication, or incorrectly configured cookies. Likewise, a website with a lower score is not automatically compromised.
Use the individual header results and raw response data to understand what needs attention rather than relying on the overall number alone.
| Problem | What it means | Recommended action |
|---|---|---|
| Missing Content-Security-Policy | The browser receives no CSP instruction from the response | Develop a policy that permits only the resources your website requires |
| Missing HSTS | The browser receives no HSTS instruction | Configure HSTS after confirming HTTPS works correctly across the relevant website and subdomains |
| Missing X-Frame-Options | No X-Frame-Options restriction is returned | Use an appropriate framing policy, such as CSP frame-ancestors, where suitable |
| Missing X-Content-Type-Options | The response does not include the expected MIME-sniffing restriction | Add X-Content-Type-Options: nosniff and configure correct MIME types |
| Missing Referrer-Policy | No explicit referrer policy is returned | Select a policy that balances privacy and website functionality |
The correct implementation method depends on your hosting environment. Apache, Nginx, LiteSpeed, managed hosting platforms, and content delivery networks may use different configuration procedures.
If you use WordPress, some security plugins and hosting dashboards provide options for configuring selected headers. However, avoid adding duplicate or conflicting headers through multiple plugins, server rules, and CDN settings.
Always test your website after making changes. A security policy that blocks required scripts, payment integrations, fonts, analytics, or embedded content can affect normal website functionality.
The Auditest HTTP Security Headers Checker is a focused baseline assessment, not a complete website security audit.
It evaluates five widely recommended HTTP security headers, but it does not cover every possible browser security policy. For example, it does not assess Permissions-Policy or cookie security attributes such as Secure, HttpOnly, and SameSite.
It also does not evaluate your TLS/SSL certificate, encryption configuration, server software vulnerabilities, database security, authentication system, or application code.
The result reflects the response observed during the live request. Different pages, server configurations, caching layers, geographic locations, or user-agent conditions may return different headers.
For a more complete picture, combine this test with other relevant security and technical checks. In particular, use the Auditest tools directory to find the SSL Checker and other website analysis tools.
Remember: A good security headers score does not certify that your website is secure, guarantee regulatory compliance, or replace professional penetration testing.
This tool is useful for several groups of website professionals:
Website owners: Identify missing browser security instructions and understand basic server security configuration.
WordPress administrators: Check whether their websites return important security headers after installing plugins or changing hosting settings.
Web developers: Verify response headers during development, deployment, and troubleshooting.
SEO professionals: Include basic technical security checks in broader website reviews without confusing security headers with direct ranking factors.
Hosting and server administrators: Inspect the headers returned by websites hosted on their infrastructure.
Digital agencies: Add a quick security-header review to website maintenance and technical audit workflows.
Whether you manage a personal blog, business website, online store, or content platform, reviewing HTTP response headers is a useful part of routine website maintenance.
An HTTP Security Headers Checker is a tool that sends a request to a website, reads the HTTP response headers, and checks whether selected browser security instructions are present and reasonably configured.
Yes. Most HTTP security headers can be configured without purchasing a separate security product. However, implementation may require access to your web server, hosting control panel, CDN, or website configuration.
No. HTTPS encrypts data exchanged between a browser and a website, but it does not automatically configure all recommended HTTP security headers. HTTPS and security headers serve different purposes and should be considered complementary protections.
Security headers are primarily browser security controls, not a direct ranking checklist. Their presence should not be treated as a guaranteed Google ranking improvement. Website owners should implement them for appropriate security and privacy reasons.
A higher score indicates that more of the five headers checked by the tool are present and reasonably configured. However, there is no universal score that guarantees website security. Review the individual results and your website's actual requirements.
No. It performs a focused check of five HTTP security headers. It does not test every possible vulnerability, inspect application code, or evaluate SSL/TLS configuration.
An SSL Checker examines aspects of your website's SSL/TLS certificate and HTTPS configuration, while the HTTP Security Headers Checker examines browser security instructions returned through HTTP response headers. Using both provides a broader view of two different areas of website security.

Website security is not achieved through a single setting. It requires a combination of secure development practices, appropriate server configuration, regular updates, and continuous monitoring.
HTTP security headers provide an additional layer of protection by telling browsers how to handle website content and certain potentially risky behaviours. Identifying missing headers is a practical first step towards improving your website's security configuration.
Use the Auditest HTTP Security Headers Checker to test your website, review the five supported security headers, inspect the raw HTTP response, and identify areas that may require attention.
Visit Auditest to explore more free website analysis, SEO, technical diagnostics, and security tools.
Author: Kester Terna, Founder of Auditest
Last Reviewed: November 2026