What is this tool?
This HTTP headers checker shows the response headers a website sends and grades its security setup from A+ to F. Enter a URL, pick HEAD or GET and a User-Agent (Wivrix checker, desktop Chrome, iPhone Safari, Googlebot or curl), and press Check Headers. The report validates the values, not just presence: HSTS max-age, CSP unsafe-inline, unsafe-eval and wildcards, X-Frame-Options or CSP frame-ancestors, X-Content-Type-Options, Referrer-Policy and Permissions-Policy. It flags deprecated headers (X-XSS-Protection, Expect-CT, HPKP, Feature-Policy) and version leaks in Server and X-Powered-By. It also audits every Set-Cookie for Secure, HttpOnly and SameSite, checks CORS, COOP/COEP/CORP and caching, and confirms that the http:// version redirects to HTTPS. You see the redirect chain hop by hop, plus copy-ready fix snippets for nginx, Apache and Cloudflare. Browsers cannot read another site's headers, so URL checks run on a Wivrix server; Paste headers mode analyses curl -I or DevTools output entirely in your browser. TLS certificates are not inspected.
How to Use
- Type the address into URL to check, for example https://example.com, or switch to Paste headers and paste curl -I output.
- Choose a Method and User-Agent, and keep Follow redirects and the HTTP-to-HTTPS check ticked.
- Press Check Headers or Enter (Ctrl+Enter in paste mode).
- Read the grade, problems and warnings, the cookie table and the redirect chain.
- Open How to fix for nginx, Apache or Cloudflare snippets, and copy the headers, report or a share link.
Frequently Asked Questions
Why is my URL sent to a server?
Browsers block pages from reading another site's response headers, so a Wivrix Cloudflare Worker fetches the URL and returns the headers. Only the URL and your options are sent, and private or internal addresses are blocked. Paste headers mode never leaves your browser.
How is the grade calculated?
Each site starts at 100 points. Missing or weak security headers, unsafe cookie flags, risky CORS, version leaks and a missing HTTP-to-HTTPS redirect cost points. A+ needs 95 or more, no problems and all six core headers passing; then A is 85+, B 70+, C 55+, D 40+ and F below that.
Should I use HEAD or GET?
HEAD is faster because no page body is downloaded, but some servers answer it differently. If a HEAD request returns 404 or 405, the checker retries with GET and says so next to the method.
Does it check my TLS certificate?
No. It reports whether the HTTPS request succeeded, but does not inspect the certificate's issuer, expiry or chain.
How many redirects does it follow?
Up to five hops, each shown with its status code, method and Location. The security headers are graded on the final response.
Other tools
There are more calculators, converters and editors on Wivrix. If something is missing, tell us.