SecurityFuse

Scanner Policy

Version 1.0.1 · Updated

Effective date:

Access and authorization

SecurityFuse is an informational website-scanning and reporting tool operated by Digital Magnet Corporation.

Hosted website scanning is available to invited users who sign in and have active access. Anonymous scanning, hosted repository assessment and company reviews are not offered in this website beta.

Before a scan, you must accept the current Terms and Acceptable Use Policy, confirm that you own the target or have permission covering the assessment, and have available scan allowance. Quick requires this authorization attestation. Deep also requires current verified ownership proof.

For Deep, choose Create HTTPS file challenge and publish the exact token bytes, with no trailing newline, at the target origin’s /.well-known/securityfuse-verification.txt path. Then choose Verify published file. The proof expires after one hour; Deep scans and rechecks require a current verified proof.

Scanner identification

The scanner identifies its requests, including ownership-file verification, with User-Agent: SecurityFuse/0.2 (+https://securityfuse.com/trust/scanner).

Limits

Quick samples one homepage and up to two same-origin scripts, with limits of ten website contacts and ninety seconds.

Deep samples a bounded set of pages from the same origin, stopping page discovery after twenty-five visited pages to reserve requests for other checks, and samples up to twenty scripts. Its limits are two hundred website contacts and ten minutes.

These are upper limits, not completion-time or response-time promises. Redirects, retries and follow-up checks consume the scan’s contact budget. Scan allowances for an account are separate from the number of requests permitted within one scan.

Creating an ownership challenge does not contact your website. HTTPS file verification is a separate bounded request, not part of the scan’s contact allowance; it does not follow redirects.

Scope and exclusions

Collection is restricted to the exact authorized public HTTPS origin and supported resources. Credentials and private or reserved destinations are rejected.

Quick checks the homepage response and a small same-origin script sample without fixed-path exposure probes. Deep adds a bounded same-origin crawl and an environment-file exposure check using a missing-path control.

The hosted website beta does not provide authenticated-browser testing, form submission, mutation requests, active exploitation, a full TLS audit, website DNS/email assessment or model analysis. TLS connection facts do not establish a complete TLS configuration review.

SecurityFuse does not apply or deploy repairs. Copying or editing a fix prompt prepares text for your own coding tool and does not execute that tool or establish that a change worked.

Reading evidence and rechecks

A report describes checks performed, assessed resources and observation time, keeping observations, inferences, coverage gaps and comparison states distinct.

A missing header alone does not establish exploitability, and an unassessed area is not a pass.

Configuration scores summarize assessed settings and must be read alongside coverage; a report or absence of findings does not certify safety, compliance or completeness.

You decide how to act and must review and test repair guidance; a repair statement is not fresh evidence.

A recheck creates a new authorized scan and compares evidence on a compatible basis without changing the earlier report. It can show newly observed, still observed, no longer observed or inconclusive results; it does not approve an application.

The sample report is from an owned test site with a fictional display target, is not customer evidence and launches no scan.

Concerns, withdrawal and target opt-outs

The owner monitors security@securityfuse.com for abuse, vulnerability reports and owner opt-out requests.

We aim to acknowledge messages within three business days, excluding weekends and Ontario public holidays and using America/Toronto local time, without a fixed resolution or exclusion-completion promise.

Credible ongoing unauthorized scanning or immediate harm is prioritized without a promise of continuous monitoring or emergency-response times.

The owner reviews target opt-out requests manually and may ask for DNS, website-file or other appropriate authority evidence; the request covers only the demonstrated scope.

The owner handles exclusion requests manually; no automated cross-account exclusion or running-scan stop service is represented as operating.

The owner manually reviews fresh authority before removing an exclusion.

Send individual withdrawal requests to hello@securityfuse.com. The owner handles the stated grant or scope manually; unrelated grants and existing records remain subject to their own authorization, retention and deletion limits.

Vulnerability reports

Report vulnerabilities in SecurityFuse itself privately to security@securityfuse.com; neither reporting nor security.txt authorizes deliberate testing without separate written scope and permission.

No bug-bounty reward or safe-harbor commitment is offered during beta, and public use of customer findings or aggregate research needs separate review and required permissions.

Security contact file

Our contact file at https://securityfuse.com/.well-known/security.txt identifies security@securityfuse.com and states its expiry. It does not grant permission for testing.

The owner maintains and renews the published contact file before expiry.

The contact file uses the canonical URL https://securityfuse.com/.well-known/security.txt and the contact mailto:security@securityfuse.com.