Free tool
Does your site send the headers that protect the visitor?
Enter the domain. The tool opens the home page as a browser would, reads the response headers and tells you what is missing, with the line ready to copy.
The result shows here: a verdict, what each header says and the line to fix it.
What each header does
- What is HSTS?
- The Strict-Transport-Security header. It tells the browser the site must only be reached over HTTPS, and the browser starts refusing the unencrypted version.
- What is the content policy (CSP)?
- A list of what the page may load and run. If someone injects a script, the policy is what stops the browser from running it.
- What is security.txt?
- A file at /.well-known/security.txt, defined by RFC 9116, that says where to report a security flaw in the site.
- Do correct headers mean a secure site?
- No. Headers are the layer the browser applies. Permission, billing and cross-customer data flaws do not show here, and they are what a manual test looks for.
- A large site got a low grade. Is it unsafe?
- That cannot be concluded. The grade speaks only of the home page headers. Very large companies also protect visitors by other means, such as the list built into the browser, and sometimes leave a header out so older systems keep working. The tool recognises that list and a policy in observation mode, but it does not see what sits behind.
- Does RET store the domain I type?
- No. The tool makes three requests to the site, returns the result and neither records the domain nor asks for an e-mail.
- What does the tool access on my site?
- The home page over HTTPS, the same page over HTTP to see whether it redirects, and the security.txt file. In public DNS, it looks up who may issue a certificate for the domain and whether the answers are signed. It also asks the public list of sites that browsers only open over HTTPS (hstspreload.org), sending only the domain name. It does not read the page content, submit forms or attempt any flaw.