Help Centre
Getting started
Headergrade is a one-shot diagnostics tool. You give it a URL, and it fetches that URL server-side, reads the HTTP response headers, and reports what it found — one header at a time, in plain language, with a copyable fix when something is wrong.
- Go to the Check a URL page.
- Enter the full URL (including
https://) of the page you want to test — or just the domain name; Headergrade will prependhttps://automatically. - Click Check. The tool fetches the URL, analyses six security headers, and displays the results within a few seconds.
- Expand any header card to see the raw value received, a plain-language explanation, and (if applicable) the one-line change to improve it.
Frequently asked questions
- Content-Security-Policy — controls which resources (scripts, styles, images, fonts) the browser may load. A strong CSP stops XSS even if an attacker injects a script tag.
- Strict-Transport-Security (HSTS) — forces HTTPS connections for a specified duration. Protects against protocol-downgrade attacks.
- X-Content-Type-Options — prevents MIME-type sniffing. Reduces risk of drive-by downloads and script-injection attacks.
- X-Frame-Options — controls whether your page may be displayed in a frame or iframe. Prevents clickjacking.
- Referrer-Policy — controls how much referrer information is sent to other origins. Affects user privacy.
- Permissions-Policy — controls which browser features (camera, microphone, location, sensors) the page and its embedded frames are allowed to use.
- Good — the header is present with a value that provides meaningful protection for most sites. You can still improve it, but there is no urgent issue.
- Weak — the header is present but has room for improvement. For example, HSTS with a short
max-ageis better than nothing but should be raised to a year. A too-permissive CSP (e.g.default-src 'self' https:without nonces) is flagged as weak. - Missing — the header was not sent at all. The tool provides a copyable snippet you can add to your server config.
- The URL is unreachable — the server was down, refused the connection, or the DNS name does not resolve.
- The server returned a non-200 status (e.g. 404, 500). The tool still reports headers from whatever response it received, but the analysis may be less useful.
- The URL uses a private or local address — the tool will not connect to IP ranges reserved for private networks.
- Rate limiting — if you send many requests in quick succession, the tool may temporarily pause additional checks. Wait a moment and try again.
Known limitations
Honest about what is and is not built
- Single URL at a time. There is no batch mode, no bulk upload, and no way to check a list of URLs in one go. Each check processes exactly one URL.
- No crawling. The tool fetches only the exact URL you type. It does not follow links, load subresources, or crawl the site. It will follow at most a couple of HTTP redirects.
- Six headers only. We check Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy. Other potentially relevant headers (e.g.
Set-CookiewithSecure/HttpOnlyflags,Cross-Origin-*headers) are not analysed. - No compliance claims. The tool does not report whether a configuration meets PCI-DSS, HIPAA, ISO 27001, or any other standard. There is no score out of 100, no grade letter, and no certification.
- No accounts or storage. You cannot save results, create a dashboard, or set up recurring checks. Every session starts fresh.
- Pro plan is not yet available. Batch checks, CSV/JSON exports, API access, and priority email support are planned but not built. The checkout form on the Pricing page is a demo illustration only — no real payment is taken.
- No notifications or alerts. There is no email sender, no SMS gateway, no webhook system. The tool cannot tell you when something changes.
How to contact us
Headergrade does not have a dedicated support email address or a ticketing system. The best way to get help, report a bug, or suggest a feature is to open an issue at the project repository.
If you have found a security-relevant bug in the tool itself (rather than a header misconfiguration on your site), please follow responsible disclosure practices: describe the issue in a repository issue without including sensitive details, and we will follow up as quickly as possible.
For questions about these FAQs or the Terms of Service, the repository issue tracker is the right place as well. We aim to respond within a few business days.