SimplyScan logoSimplyScan
What We ScanPricingFree ToolsBlogCreate AccountLog In
  1. Home
  2. Free Tools
  3. Security Headers Checker
Free Tool

Free Security Headers Checker

Get an A-F grade on your site's HTTP security headers, including CSP, HSTS, and cross-origin isolation policies.

Free account required to run the check. What you type here is kept through sign-in.

How to use it

  1. Enter the full URL of the page you want to grade, for example https://example.com.
  2. Run the check. SimplyScan requests the page once from its servers and reads the response headers it gets back.
  3. Read the grade and the list underneath: each header shows whether it is missing, present but weak, or passing.
  4. Fix the weakest headers first (Content-Security-Policy and Strict-Transport-Security carry the most weight), redeploy, and run the check again.

Example

A typical site that sets the easy headers but has no Content-Security-Policy yet.

Input

https://example.com

Result

Grade C · 67 / 100

✗ Content-Security-Policy        Missing header.
✓ Strict-Transport-Security      max-age=31536000; includeSubDomains
✓ X-Frame-Options                DENY
✓ X-Content-Type-Options         nosniff
✓ Referrer-Policy                strict-origin-when-cross-origin
✓ Permissions-Policy             camera=(), microphone=(), geolocation=()
✓ Cross-Origin-Opener-Policy     same-origin
✗ Cross-Origin-Embedder-Policy   Missing header.
✗ Cross-Origin-Resource-Policy   Missing header.
✓ Third-party script integrity
✓ HTTP to HTTPS redirect order

What each header does

Content-Security-Policy (25 points)
Tells the browser which scripts may run. It is the main defence against cross-site scripting. It only earns credit when script-src (or default-src) avoids 'unsafe-eval', avoids 'unsafe-inline' unless you use nonces or hashes, and doesn't allow every https: source.
Strict-Transport-Security (20 points)
Makes browsers use HTTPS for your domain on every later visit, so nobody can downgrade a visitor to plain HTTP. The max-age must be at least 15552000 seconds (six months) to count.
X-Frame-Options (10 points)
DENY or SAMEORIGIN stops other sites from loading your pages in a hidden frame, which is how clickjacking works.
X-Content-Type-Options (10 points)
nosniff stops browsers guessing a file's type, so an uploaded file can't be run as a script.
Referrer-Policy (10 points)
Controls how much of your URL is sent to other sites when someone clicks a link. strict-origin-when-cross-origin, same-origin, strict-origin and no-referrer all pass.
Permissions-Policy (10 points)
Switches off browser features your site doesn't use. It passes when camera, microphone or geolocation is turned off with =() and nothing is opened to everyone with =*.
Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy (7 and 8 points)
same-origin, and require-corp or credentialless, isolate your page from other windows and embedded content. COEP can break third-party embeds, so test it before you ship it.
Cross-Origin-Resource-Policy, script integrity and redirect order (5 points each)
Whether other sites may load your resources, whether third-party scripts carry an integrity hash, and whether http:// redirects straight to https:// on the same host.
Present but weak or invalid
The header exists but its value doesn't protect anything, for example an HSTS max-age of a few minutes. It gets no credit until the value is fixed.
Grade bands
The points you earn are turned into a score out of 100: A is 90 and above, B 75, C 60, D 45, E 30, and F below that.

Set the headers on your platform

Start Content-Security-Policy in report-only mode, or with a loose policy, and tighten it once nothing breaks. The other headers below are safe for most sites.

Vercel (vercel.json)

{
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        { "key": "Strict-Transport-Security", "value": "max-age=31536000; includeSubDomains" },
        { "key": "X-Frame-Options", "value": "DENY" },
        { "key": "X-Content-Type-Options", "value": "nosniff" },
        { "key": "Referrer-Policy", "value": "strict-origin-when-cross-origin" },
        { "key": "Permissions-Policy", "value": "camera=(), microphone=(), geolocation=()" },
        { "key": "Cross-Origin-Opener-Policy", "value": "same-origin" }
      ]
    }
  ]
}

Netlify and Cloudflare Pages (_headers file in the published folder)

/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains
  X-Frame-Options: DENY
  X-Content-Type-Options: nosniff
  Referrer-Policy: strict-origin-when-cross-origin
  Permissions-Policy: camera=(), microphone=(), geolocation=()
  Cross-Origin-Opener-Policy: same-origin

Next.js (next.config.js)

module.exports = {
  async headers() {
    return [{
      source: "/(.*)",
      headers: [
        { key: "Strict-Transport-Security", value: "max-age=31536000; includeSubDomains" },
        { key: "X-Frame-Options", value: "DENY" },
        { key: "X-Content-Type-Options", value: "nosniff" },
        { key: "Referrer-Policy", value: "strict-origin-when-cross-origin" },
      ],
    }];
  },
};

Go deeper

  • A Security Headers Checklist for AI-Built Apps
  • How to Check and Configure Security Headers in Next.js Apps
  • Content Security Policy for Vibe-Coded Apps: A Practical CSP Guide
  • CSRF Protection & Security Headers: The Missing Layer in AI-Built Apps

Page updated 21 November 2026

Frequently asked questions

Which headers do you check?

Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy, and Cross-Origin-Embedder-Policy.

How is the grade computed?

Each header carries a weight based on impact. Present headers earn their weight; the total is normalized to 0-100 and mapped to A through F.

Why is my grade low when the site works fine?

Security headers don't change how a page looks. They limit what an attacker can do if something else goes wrong, such as an injected script or a hostile site framing your page. A working site with no headers simply has no second line of defence.

Can a missing header break my site when I add it?

Content-Security-Policy and Cross-Origin-Embedder-Policy can, because they block scripts or embeds that aren't allowed. Roll those out in report-only mode first. HSTS is hard to undo, because browsers remember it for the whole max-age, so make sure every subdomain serves HTTPS before you add includeSubDomains.

Which page should I check?

Your homepage plus one signed-in page, such as the dashboard. Many hosts set headers per route, so the two can differ.

Is anything sent besides the URL?

SimplyScan's servers request the URL you enter, once, and read the response headers and HTML. They don't send cookies, sign in or submit forms.

Want the full picture?

This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.

Run a full security scan

Related tools

Email Security Checker

Check your domain's email authentication · SPF, DKIM, and DMARC · and see if you're vulnerable to spoofing.

DNS Security Checker

Check whether a domain is protected by DNSSEC and restricts certificate issuance with CAA records · two defenses against DNS hijacking and rogue certificates.

DNS Lookup

Query any domain's DNS records live · A, AAAA, CNAME, MX, TXT, NS, and CAA · resolved over encrypted DNS-over-HTTPS.

SimplyScan logoSimplyScan

Security Scanner for Vibe-Coded Apps.

Product

See What We ScanHow It WorksView PricingFeedback

Resources

Security BlogSecurity ChecklistTrust BadgeUptime MonitoringIntegrationsMCP Server (Claude, Cursor & Windsurf)API DocumentationBackend Audit GuideThreat Detection GuideFAQTerms of ServicePrivacy Policy

Platforms

All platforms →Lovable ScannerBolt.new ScannerCursor ScannerReplit Scannerv0.dev ScannerWindsurf ScannerBubble Scanner

Free Tools

All free tools →SSL CheckerSecurity HeadersDNS Security CheckerCORS TesterJWT DebuggerCSP EvaluatorHash GeneratorSEO Checker

Account

Create AccountLog In

© 2026 SimplyScan. All rights reserved.