Skip to main content
VirtualVenture
Free tool · Security

Security Headers Checker

Check which HTTP security headers your site sends, see whether each one is set well, and copy the exact fix for your web server or CDN.

A+ to F grade, rules shown Checks values, not just presence Fixes for 6 servers & CDNs No sign-up

We fetch the page once from Virtual Venture's server, as an outside visitor would, and read its response headers. Private and internal addresses are refused. Nothing is stored unless you download the PDF report.

The six headers that matter most

Strict-Transport-Security (HSTS)

Forces HTTPS for your domain for the max-age you set, so a visitor on public Wi-Fi can't be silently downgraded to HTTP. Recommended: max-age=31536000; includeSubDomains.

Content-Security-Policy (CSP)

A list of places scripts, styles, images and frames may load from. It's the strongest browser-side defence against XSS, but it must match your site, so roll it out in report-only mode first.

X-Frame-Options

Stops your pages being embedded in someone else's frame for clickjacking. SAMEORIGIN suits most sites. The modern equivalent is CSP frame-ancestors.

X-Content-Type-Options

One value, nosniff. It stops browsers treating a file as a different type than you declared — for example running an uploaded text file as JavaScript.

Referrer-Policy

Decides how much of the current URL is sent to other sites. strict-origin-when-cross-origin sends only your domain to other sites and keeps full paths (which can contain tokens) private.

Permissions-Policy

Turns off browser features you don't use, such as camera, microphone and geolocation, so injected or third-party scripts can't request them.

About this tool

What it checks

  • Whether each of the six key security headers is sent
  • Whether each value is actually strong (HSTS age, unsafe CSP sources, obsolete X-Frame-Options)
  • Optional cross-origin isolation headers and server software disclosure
  • Ready-to-paste fixes for nginx, Apache, IIS, Express, Netlify and AWS CloudFront

How it works

  1. 1You enter a public URL; Virtual Venture's server fetches it once through an SSRF-hardened request.
  2. 2The response headers of the final page (after redirects) are read exactly as an outside visitor receives them.
  3. 3Each header is graded against the documented rubric, and weak values are explained.
  4. 4A fix snippet is generated only for headers that are missing or weak.

Example output: Grade C (60/100): HSTS good, X-Content-Type-Options good, X-Frame-Options good, Content-Security-Policy missing, Permissions-Policy missing — with a one-click nginx snippet adding a report-only CSP and a Permissions-Policy.

Frequently asked questions

They are response headers your web server sends with every page that tell the browser how to behave more safely: always use HTTPS (HSTS), only run scripts from trusted places (CSP), don't allow framing (X-Frame-Options), don't guess file types (X-Content-Type-Options), limit what's shared with other sites (Referrer-Policy) and switch off unused browser features (Permissions-Policy). They're cheap to add and block whole classes of attacks.

Know someone who'd find this useful?

Share this free tool — it's free for everyone, with no sign-up.

Found this tool useful? Help keep it free.

Our tools have no sign-up, no ads and no paywall. A one-time contribution of any amount covers servers and funds new tools.

Donate

Need help?

Chat with us on WhatsApp