HTTP Security Headers Checker
Inspect supported HTTP security headers including HSTS, Content-Security-Policy, and X-Frame-Options to harden your website against browser-side vulnerabilities.
How to Use This Tool
Run an automated assessment in three straightforward steps.
Enter Web Address
Input your website domain (e.g. example.com). No code modifications or server installations are necessary.
Inspect HTTP Response
SiteSecura sends standard HTTP GET and HEAD requests, parsing every response header returned by your web server or CDN.
Copy Remediation Snippets
Review missing headers with exact syntax recommendations ready to paste into Nginx, Apache, or Cloudflare.
Inspected HTTP Response Headers
SiteSecura checks whether your server returns defensive response headers and evaluates their directive configurations.
Strict-Transport-Security (HSTS)
HTTPS EnforcementInstructs modern browsers to communicate strictly over encrypted HTTPS connections, preventing SSL stripping and downgrade attacks.
Content-Security-Policy (CSP)
XSS DefenseRestricts the origin domains from which scripts, styles, images, and fonts can load, mitigating Cross-Site Scripting (XSS) and data injection.
X-Frame-Options
Clickjacking ProtectionControls whether the website can be rendered inside an <iframe> or <frame>, blocking UI redress and clickjacking attacks.
X-Content-Type-Options
MIME-Sniffing DefensePrevents browsers from MIME-type sniffing executable scripts disguised as user-uploaded images or text files (nosniff).
Referrer-Policy
Data PrivacyGoverns how much sensitive referrer path data (including query parameters and session tokens) is leaked to external sites when navigating.
Permissions-Policy
Feature GovernanceExplicitly disables browser hardware access (e.g. camera, microphone, geolocation) that your web application does not need.
Interpreting Scan Results
Every scan item receives an explicit status indicator to help you prioritize remediation.
The header is configured with secure recommended directives (such as max-age >= 1 year for HSTS).
The header is present but contains weak directives (such as short max-age, missing includeSubDomains, or permissive CSP).
An essential defensive browser header is entirely absent from production HTTPS responses.
Observed server banners (such as Apache, Nginx, or Cloudflare) and optional privacy directives.
Practical Remediation Guidance
How to resolve common gaps and harden your server configurations.
Configuring defensive HTTP response headers is one of the quickest and highest-ROI security enhancements you can make. Here are production-ready baseline snippets:
# 1. Enforce HTTPS strictly for 1 year including subdomains add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always; # 2. Prevent clickjacking add_header X-Frame-Options "SAMEORIGIN" always; # 3. Disable MIME-sniffing add_header X-Content-Type-Options "nosniff" always; # 4. Restrict Referrer leakage add_header Referrer-Policy "strict-origin-when-cross-origin" always; # 5. Disable unused hardware features add_header Permissions-Policy "geolocation=(), microphone=(), camera=()" always;
<IfModule mod_headers.c> Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" Header always set X-Frame-Options "SAMEORIGIN" Header always set X-Content-Type-Options "nosniff" Header always set Referrer-Policy "strict-origin-when-cross-origin" </IfModule>
Assessment Limitations & Technical Scope
SiteSecura performs deterministic, non-intrusive perimeter checks. Understanding what a passive assessment cannot evaluate ensures responsible risk management:
- •Security headers instruct client browsers; they cannot protect against backend server compromise or database vulnerabilities.
- •A missing header is not automatically a critical flaw; impact depends on application features (e.g. whether user content is hosted).
- •Does not dynamically execute all JavaScript or evaluate complex CSP nonces on deep authenticated dynamic paths.
- •Web applications with existing legacy inline scripts may require gradual refactoring before enabling strict CSP.
- •Header presence alone does not guarantee safety if policies use overly permissive wildcards (e.g. `script-src *`).
Recommended Technical Guides
Learn defensive concepts and architectural best practices from our engineering team.
Related Security Utilities
Explore dedicated perimeter verification tools in the SiteSecura toolkit.
Website Security Scanner
Run an integrated evaluation covering HTTPS, certificates, security headers, and domain email authentication.
SSL/TLS Certificate Checker
Inspect certificate expiration dates, CA issuer chain, SAN domain matching, and supported TLS protocol versions.
SPF, DKIM & DMARC Checker
Audit DNS email-authentication records to stop domain spoofing and phishing.
Frequently Asked Questions
Ready for a Complete Website Security Evaluation?
Run an end-to-end passive scan across HTTPS, SSL certificates, defensive HTTP response headers, and DNS email authentication records in under 60 seconds.