Scans
The Scans page gives you a complete history of every scan that has been executed across all your domains. It's your control center for monitoring scan progress, reviewing logs, and managing scan lifecycle.
Accessing Scans
Click Scans in the sidebar.
Launching a Quick Scan
At the top of the page, you can launch a scan directly:
For more control over scan configuration (choosing specific modules, setting rate limits, etc.), use the scan dialog from the Domains page instead.
Scans Table
The table lists all scans with the following columns:
ID — Unique scan identifier
Domain — The domain being scanned (click to go to its Results Dashboard)
Type — The scan type (e.g., recon, full, general_scan, xss, etc.)
Status — Current status:
Pending — Queued and waiting to start
Running — Currently executing
Completed — Finished successfully
Failed — Encountered an error
Stopped — Manually stopped by the user
Progress — Percentage completion for running scans
Started — When the scan began
Finished — When the scan completed
Filtering and Sorting
Status filter — Show only scans with a specific status (Running, Completed, Failed, etc.)
Type filter — Filter by scan type
Sort — Click column headers to sort by any field. Default sorting is by start time (newest first).
Scan Actions
Each scan row has action buttons:
View Logs — Opens a dialog showing the detailed execution logs for that scan. This is useful for debugging failed scans or understanding what happened during execution.
View Results — Navigate to the scan's detailed results page
Stop Scan — Gracefully terminates a running scan. A confirmation dialog appears before stopping.
Delete Scan — Permanently removes the scan and all its associated results. A confirmation dialog appears before deletion.
Understanding Scan Types
Scans in Ryft follow a parent-child relationship (see How Scanning Works for details):
Parent scans are the main reconnaissance scans that discover your attack surface. When you launch a "Full Scan" from the Domains page, the parent scan runs first.
Child scans are individual vulnerability or cloud modules that run after reconnaissance. Each module (e.g., general_scan, xss, s3_buckets) creates its own child scan.
The Scans table shows both parent and child scans. Child scans are linked to their parent, so you can trace which reconnaissance scan triggered which vulnerability tests.
Pagination
Scans are paginated server-side for performance. Use the pagination controls to navigate through your scan history. You can display 15, 50, or 100 scans per page.
Last updated