Scan History

Unbounded archive of every completed and failed scan, suitable for audit, period reports, and forensic exploration. Auto-refresh is off by default; refresh manually when needed.

Inputs

Name	Description	Allowed values	Default
`From date`	Show scans started on the selected day onward (sent as that day's UTC midnight via startedAfter, an exclusive `>` bound — every scan started during the day is included)	Any date in YYYY-MM-DD format	No lower bound (full archive)
`To date`	Show scans started on or before the selected day (the UI sends the following day's UTC midnight via startedBefore, an exclusive `<` bound, so the chosen To day is fully included)	Any date in YYYY-MM-DD format	No upper bound (full archive)
`Status column filter`	Per-column filter dropdown in the Status header	Completed, Failed	Both shown
`Started By column filter`	Per-column filter dropdown in the Started By header	Any user who has run a scan	All users

Fields & columns

Name Description

Reverse DNS The scan execution's reverse-DNS enrichment status — not a per-host result. One of six values: Collecting (the scan is still feeding the enrichment hosts to look up), Closing, Complete, Incomplete, Cancelled, or "—" (reverse DNS was not requested for this scan, or the status read itself failed). The same words the scan's reverse-DNS summary box uses. Hidden by default; enable it from the column gear icon. Not sortable: the status is merged in after the page of scans is read. Per-host hostnames and DNS status live on the scan's results page.

Name	Description
`Reverse DNS`	The scan execution's reverse-DNS enrichment status — not a per-host result. One of six values: Collecting (the scan is still feeding the enrichment hosts to look up), Closing, Complete, Incomplete, Cancelled, or "—" (reverse DNS was not requested for this scan, or the status read itself failed). The same words the scan's reverse-DNS summary box uses. Hidden by default; enable it from the column gear icon. Not sortable: the status is merged in after the page of scans is read. Per-host hostnames and DNS status live on the scan's results page.

How to

Search Scan History

Open the Scan History page — it loads the most recent scans.
Use the Status, Template, and Started By dropdowns above the table to narrow results.
Enter a From and/or To date to bound the search — both filter at day granularity (From shows the selected day onward; To includes the whole selected day).
Toggle additional columns via the gear icon — the full superset includes Tests breakdown, Duration, and Completed timestamp.
Click a row to navigate to that scan's full results page.

Export Scan Data

Apply your filters and date range.
Click the export menu in the table footer.
Choose CSV, JSON, or PDF format.
Share the file with auditors or include in period reports.

Gotchas

Each completed row has a "View changes" link to its port-state diff (opened/closed ports vs the previous scan of the same template).
For day-to-day triage you probably want Recent Scans — History returns everything, which can be slow and noisy if you're just looking for last shift's runs.
Click a row to navigate to that scan's results. Whole-row click works on every completed/failed scan.
The list opens newest first. Tests, Findings and Reverse DNS cannot be sorted: they are added to each row after the page of scans is read, so there is nothing for the server to order by.
Export is rendered client-side from the currently-loaded rows (CSV/JSON/PDF via the table footer). Server-side export is not yet wired — narrow filters first if you want a smaller export.
The Reverse DNS column is opt-in (hidden by default) — toggle it on via the gear icon for a deployment that uses reverse-DNS resolvers. Most scans never request reverse DNS, so a column full of "—" would be dead weight on the default view.

API calls (1)

Method	Path	Description
GET	`/api/scans`	Fetch scans filtered by status=completed,failed; supports startedAfter, startedBefore, limit, offset, and sort + dir (sort is a column key: id, template, status, startedBy, started, completed or duration; any other value is a 400)

Running Scans — Monitor scans currently executing or pending dispatch
Recent Scans — View scans from your configured time window for quick triage