Web security

security.txt published

Security headers, HTTPS enforcement, cookies and cross-origin rules of the website.

Why it matters

Security researchers who find a problem have no clear way to tell you, so the report may never arrive - or the issue is disclosed publicly first.

How to fix it

Quick fix · under 1 hour

Create /.well-known/security.txt with at least Contact and Expires.
Use an address that is monitored.

/.well-known/security.txt

Contact: mailto:[email protected]
Expires: 2027-12-31T23:59:59Z
Preferred-Languages: en

How we test it

The check runs from the public internet as part of every scan, read-only and without touching your data. If it fails, your report shows the evidence that proves it - the record, header, file or banner we observed - together with the fix above, tailored to the issue we found.

Does your domain pass this check?

Run all 97 checks in about a minute. Your first scan is free, with the complete fix for your most urgent finding.

Scan your domain free