PureDevTools

HTTP Header Analyzer

Paste response headers — analyze security, caching, CORS, and content-type settings

All processing happens in your browser. No data is sent to any server.

Copy from browser DevTools → Network → Response Headers, or from curl -I <url>

Paste HTTP response headers to analyze security headers (CSP, HSTS, X-Frame-Options), caching directives, CORS settings, and content type configuration. No network requests are made.

You copy the response headers from a browser DevTools network tab or a curl -I command and want a quick assessment of the security posture, caching configuration, and CORS settings — without manually looking up every header. Paste them here and get an instant analysis.

Security Headers Analyzed

Content-Security-Policy (CSP)

Controls which resources the browser is allowed to load. A missing or overly permissive CSP is one of the most common web security vulnerabilities. This tool parses the directives and flags dangerous values like unsafe-inline, unsafe-eval, and wildcard sources.

Strict-Transport-Security (HSTS)

Forces HTTPS connections. The tool checks max-age, includeSubDomains, and preload directive presence. A max-age below 1 year (31536000 seconds) is flagged as weak.

X-Frame-Options

Prevents clickjacking by controlling whether the page can be embedded in a frame. DENY or SAMEORIGIN are acceptable; a missing header is a warning.

X-Content-Type-Options

Should be nosniff to prevent MIME-type sniffing attacks. Any other value or absence is flagged.

Referrer-Policy

Controls how much referrer information is included with requests. strict-origin-when-cross-origin or stricter is recommended.

Permissions-Policy

Controls access to browser features (camera, geolocation, etc.). Optional but good practice to include.

Caching Headers Analyzed

How to Get Response Headers

Browser DevTools

  1. Open DevTools → Network tab
  2. Click any request
  3. Scroll to “Response Headers” section
  4. Copy all headers

cURL

curl -I https://example.com
# Or with all headers including response body headers:
curl -D - https://example.com -o /dev/null

HTTPie

http --headers GET https://example.com

Node.js / fetch

const res = await fetch('https://example.com');
res.headers.forEach((value, name) => console.log(`${name}: ${value}`));

Frequently Asked Questions

Does this tool make any network requests? No. This tool only analyzes headers you paste into it. It does not fetch any URLs or make any network connections.

What header format is expected? Standard HTTP response header format: one header per line, Name: Value. HTTP/1.1 status lines (HTTP/1.1 200 OK) are ignored automatically.

Why is my CSP flagged even though it looks restrictive? Common false-positive causes: 'unsafe-hashes' is present, or a source list includes http: or https: wildcards that allow loading from any domain over that scheme.

What does a missing security header mean? Missing headers are flagged as warnings rather than errors. The severity depends on the header — a missing X-Content-Type-Options is low risk on most sites; a missing CSP is more significant for sites handling user input.

Related Tools

More Network Tools