Toolsky

Free Online Tools & Utilities for Every Task.

Security Headers & Web Firewall (WAF) Auditor

Audit your website for security headers, detect Web Firewalls (WAF), and improve your site's protection.

Plenty of site owners believe they are protected: the hosting advert said "firewall included", a CDN account was created last spring, someone installed a security plugin once. Belief is not verification. This security headers and WAF auditor tests what is actually in front of your website — it inspects the security headers your site serves and probes for the fingerprints of a web application firewall (WAF), so you can see whether the protection you think you have is really standing between your site and the internet, and how it is configured.

Two Layers: Headers and the Firewall in Front

These two defences work at different depths, and confusing them is common. Security headers are instructions your server sends to each visitor's browser — policies about encryption, framing, script sources and data leakage that govern behaviour after a page arrives. A WAF works earlier: it sits in front of your application, inspects every incoming request, and blocks the ones that look like attacks — SQL injection strings, known exploit patterns, malicious bots, credential-stuffing floods — before they ever reach your code. A CDN-based WAF (the kind fronting millions of sites) also absorbs traffic floods at the network edge. The layers complement each other: the WAF filters hostile requests on the way in, headers restrain what browsers may do with responses on the way out. A site can have either without the other, which is precisely why this auditor reports on both in a single pass.

What This Auditor Detects

  • Core security header coverage — HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy: which are served, which are missing, and whether the values enforce anything meaningful.
  • WAF presence and identity — tell-tale fingerprints in response headers, cookies and server behaviour that reveal a firewall layer and often which provider operates it.
  • Edge versus origin clues — signs of whether requests terminate at a protective proxy or reach your origin server directly, including headers that expose the origin's own software.
  • Configuration red flags — a detected WAF undermined by a bypassable setup, headers contradicted between the edge and the application, or version banners leaking through the very layer meant to hide them.
  • One report for a layered picture — run it alongside our Security Headers Auditor for a headers-only deep dive, the Open Port Checker for exposed services, and the Browser Fingerprint Audit to see the visitor side of the equation.

How to Run a WAF and Headers Audit

  1. Enter your site's public address exactly as visitors use it, https included.
  2. Run the audit; the tool collects the site's responses and examines both the headers served and the behavioural fingerprints of any firewall layer.
  3. Check the WAF verdict first: detected or not detected, and if detected, which provider the evidence points to.
  4. Compare that verdict with what you believe you configured — a mismatch either way is the audit's most valuable finding.
  5. Work through the header findings next, noting missing policies and weak values.
  6. Fix issues at the layer responsible — CDN/WAF dashboard for edge settings, server configuration for origin headers — then re-audit to confirm the public view has changed.

What an Audit of a Protected Site Looks Like

Run this against a site properly fronted by a major CDN firewall and the fingerprints show immediately: a cf-ray style request identifier header, a Server value naming the CDN rather than the origin software, and WAF-set cookies — the edge is answering, not your server. The header list is typically strong too: HSTS enforced, frame protection present, content-type sniffing disabled, because reputable edges inject sensible defaults. Contrast a site whose owner thought the CDN was active: the audit finds no firewall fingerprints at all, the origin's full software banner exposed, and DNS pointing straight at the hosting server — the CDN account existed, but the domain was never actually routed through it. That second scenario is more common than anyone admits, and it is undetectable from inside the dashboard. Only an outside-in check like this one shows the truth.

False Comfort: What a WAF Cannot Do

A detected WAF is not an all-clear, and treating it as one is the deepest trap in this area. A WAF recognises known attack patterns; it cannot fix a plugin whose vulnerability has no signature yet, and it cannot save an admin account protected by a weak password — login attacks that use real credentials look like ordinary traffic. If your origin server's real IP address is discoverable (in old DNS records, email headers or certificate logs), attackers can bypass the edge entirely and talk to the server directly, making the firewall decorative. Headers, meanwhile, do none of the WAF's job: they never inspect a request. The honest picture is defence in depth — patched software, strong authentication, a correctly routed WAF, and sound headers — with audits like this confirming each layer is genuinely present rather than assumed. The OWASP Secure Headers Project is the reference worth bookmarking for the header half of that picture.

Frequently Asked Questions About the WAF and Headers Auditor

How can a tool detect a WAF without logging into my site?

Firewalls leave fingerprints: characteristic headers, cookies, response pages and server banners added by the edge layer. The auditor reads those public signals — the same ones an attacker would use for reconnaissance.

My report says no WAF detected, but I pay for a CDN. What happened?

Usually the domain is not actually routed through the CDN — DNS still points at your origin — or the CDN's firewall tier is not enabled. Check your nameservers and proxy status in the CDN dashboard.

Does a WAF replace keeping my site updated?

No. A WAF blocks known attack patterns but cannot repair vulnerable code, and novel exploits may have no pattern to match. Updates close the holes; the WAF buys you time and filters the noise.

Can attackers bypass a WAF?

Yes, if they find your origin server's real IP address and it accepts direct connections. Lock the origin to accept traffic only from your firewall provider's network ranges.

What is the difference between this and the headers-only auditor?

This tool adds firewall detection and the edge-versus-origin picture to the header analysis. The headers-only auditor goes deeper on header values alone; together they cover the configuration from both sides.

Will running an audit trigger my own WAF or get me blocked?

An audit reads ordinary responses and standard fingerprints; it is not an attack simulation. Well-configured firewalls do not block passive inspection of publicly served headers.

Should small sites bother with a WAF at all?

Yes — automated attacks do not check your turnover first. Bots scan every site for the same known holes, and a CDN-tier WAF is often free or bundled, making it the cheapest layer most small sites can add.

Know What Is Actually Standing Guard

Security you have verified beats security you merely believe in. One outside-in audit tells you whether a firewall truly fronts your site, whether its headers back it up, and where the gaps between assumption and reality have been quietly living.