Documentation

Getting started

This guide covers website scans in the current invite-only beta.

1. Sign in with your invited account. Use the Sign in link to open the product. Beta access requires an invitation.

2. Review the policies. Accept the Terms of Service and Acceptable Use Policy in the product. Read the separate Privacy Policy and Cookie Notice for how data and preferences are handled.

3. Start a Quick scan. Enter the website target, select Quick and confirm that you are authorized to scan that target within the selected scope. Choose Start Quick scan when your account has allowance available.

4. Read the evidence and coverage. Review what was observed and what was unavailable or outside scope. Unknown coverage is not a pass; a score or report does not certify that the website is safe.

5. Prepare a repair. On a supported finding, choose Copy fix prompt and review it with your coding tool. Apply, test and deploy changes yourself. Copying the prompt does not execute a repair or verify that it worked.

6. Verify ownership for Deep. Select Deep and choose Create HTTPS file challenge. Publish the exact token bytes, with no trailing newline, at the exact target origin’s /.well-known/securityfuse-verification.txt path. Choose Verify published file, then confirm authorization and choose Start Deep scan. Create a new challenge if the proof expires.

7. Recheck after deployment. Start a new authorized scan and compare evidence on compatible coverage. Deep requires current verified ownership proof. A repair statement alone does not change the evidence; incomplete comparisons remain inconclusive.