Practical answers about scans, findings, uptime, incidents, the public Status Page, administration, sessions and troubleshooting.
Open the Dashboard, follow the highlighted Next best action, launch one authorized scan, configure one uptime target and test alerts.
The top header displays the account name and email. If no account is active, it displays Not signed in.
The version is displayed at the top-left of the sidebar, under Security Analyzer.
No. You must own the target or have explicit authorization. The confirmation in New scan is mandatory.
Use quick for a fast baseline, standard for normal audits and deep when you accept a longer and broader execution.
Open Scan jobs and read the live log. Common causes include missing tools, permission problems, license validation, timeout or a blocked pre-flight check.
No. The score reflects automated coverage. Review the decision, findings, skipped tools and timeout tools.
Runs is the chronological history. Targets groups those runs by website.
Only after a real correction has been applied. Use Retest needed when a new scan must confirm the fix.
It means the issue is understood and deliberately accepted as a documented business decision.
A scanner result that does not apply after technical validation. It must not be used simply to hide an inconvenient finding.
The scheduler needs stored probes in the selected time window. Run Test now or wait for scheduled collection.
Use it when the normal response is not HTTP 200, for example 401, 403 or 405 on a deliberately protected endpoint.
No. It stops future scheduled checks. Existing probes and incidents remain stored unless explicitly deleted.
One central scheduler handles all active users and all monitored targets. A new systemd service is not created per user or per site.
An incident is opened when monitoring detects an outage state that is not already represented by an open incident.
Normally recovery closes them automatically. Manual resolution is for correcting an exceptional operational state.
Test incidents remain available for validation but can be excluded from production SLA and incident reporting.
It is reachable without dashboard authentication when enabled, but only through its non-guessable token URL.
Open Configure uptime, edit the target and set Public status page to hidden.
It is no longer scheduled and is never published on the public Status Page.
These pages are restricted to configured owner accounts.
It deletes dashboard scan history from SQL. It is destructive and requires a backup and owner authorization.
Use Logout in the top-right header or the existing Logout entry in the sidebar.
The configured session lifetime is seven days unless the session is invalidated earlier by logout or expiration.
Provide the Analyzer version, exact page, action, timestamp, visible error and relevant sanitized log lines. Never include secrets.