admin@likeapro.dev: ~/curl — zsh

// admin tools · 24

HTTP header checker

Follow a URL's redirect chain, read every response header and get an A+ to F grade on HSTS, CSP and the rest — with the nginx or Apache line that fixes each finding.

// --check: the URL is fetched by likeapro.dev's server, not your browser · --paste runs locally

method

Our server requests the URL (up to 8 redirects) and returns the status and headers of each hop. Private and internal addresses are refused; nothing is stored. Some servers answer HEAD differently from GET.

CHECK --check via likeapro.dev · --paste local --:--:--

How it works

What it does

Give it a URL and it follows every redirect, showing each hop's status code, address and timing, then lists all response headers. The final response is graded A+ to F on six core security headers, with a plain-English note and a copy-ready nginx or Apache line for every problem. It also summarises caching, cookie flags, compression, HTTP version and the CDN in front of the site.

What is sent: browsers are not allowed to read another site's response headers, so --check asks our fetch.php endpoint on likeapro.dev to make the request and return the headers. --paste grades output you paste from curl -sIL or DevTools, entirely in your browser.

How the grade works

Each of these counts once: Strict-Transport-Security (at least six months), Content-Security-Policy, X-Content-Type-Options: nosniff, frame protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy and Permissions-Policy. Six is an A, five a B, and so on down to F. An A+ also needs a CSP without 'unsafe-inline' or 'unsafe-eval', HSTS of a year or more with includeSubDomains, no version numbers in Server or X-Powered-By, and no risky cookies. Pages served over plain HTTP get an F.

What the other sections mean

COOP / COEP / CORP
Cross-origin isolation headers. Optional for most sites; shown for information.
cookies
Each Set-Cookie is checked for Secure, HttpOnly and SameSite, and for the rules behind __Host- and __Secure- prefixes.
caching
Cache-Control, ETag, Last-Modified, Age and Vary turned into one sentence about how long browsers and CDNs keep the response.
deprecated
X-XSS-Protection, Expect-CT and Public-Key-Pins no longer help; the tool tells you to drop them.

FAQ

Why does my site show different headers here than in my browser?

CDNs and servers can vary headers by user-agent, cookies or region, and some add security headers only to HTML responses. Our check sends no cookies. Compare with curl -sIL from your own machine using --paste.

Should I add the nginx line to every location block?

Yes, if a location has its own add_header. nginx only inherits add_header directives from the parent block when the child defines none — a common reason headers vanish on some paths. Keep always so they also apply to error responses.

Is a strict CSP worth the effort?

For anything with logins or user content, yes. Start with Content-Security-Policy-Report-Only, fix the violations it reports, then enforce it.

Can it check sites on my local network?

No — the server refuses private and internal addresses. Run curl -sIL locally and use --paste.