Documentation
Getting started with website scans.
This guide covers website scans in the current invite-only beta. Quick scans need your authorization; Deep scans also need ownership verification.
Before you scan
Sign in with your invited account
Beta access requires an invitation. Use the account you were invited with.
Sign in Opens
app.securityfuse.com/sign-inReview 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.
Quick scan
Needs your confirmation that you are authorized.
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.
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.
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.
Recheck after deployment
Start a new authorized scan and compare evidence on compatible coverage. A repair statement alone does not change the evidence; incomplete comparisons remain inconclusive.
Deep scan ownership verification
Deep needs everything Quick needs, plus current verified ownership proof covering the site you are scanning. Pick the method that matches the access you already have.
Choose a verification method
Select Deep and pick one of the two methods shown. The DNS record is set up once: choose it when you can edit DNS for the domain. One record covers the domain you select for verification and its subdomains, so other sites under that domain need no new setup. The verification file is a one-hour proof: choose it when you can deploy to the site but cannot change its DNS, or when the host is on a shared public suffix, such as a hosting platform's domain.
Publish the proof
For the DNS record, choose Add DNS verification for the domain you select for verification, then add a TXT record at your DNS provider with this name and the value shown in the product:
_securityfuse-verification.<your domain>Keep the record published. It is checked again when you start a Deep scan or recheck, and again before collection. If you remove it, later Deep scans and rechecks using it are blocked; a scan already collecting is not stopped. DNS changes can take time to appear, and a failed check keeps the same saved value, so publish it and check again.
For the verification file, choose Create HTTPS file challenge and publish the exact token bytes, with no trailing newline, at this path on the exact target origin:
/.well-known/securityfuse-verification.txtVerify and start
Choose Check now for the DNS record, or Verify published file for the verification file. Then confirm authorization and choose Start Deep scan. Verification alone never starts a scan.
The file proof covers that one origin only, expires after one hour and is not renewed automatically; create a new challenge if the proof expires. Every scan, including every recheck, needs its own authorization confirmation. A Deep recheck also needs a current proof: a still-published verified DNS record, or a file proof less than one hour old.