mipo

Recent Scans

Quick-triage view of completed and failed scans within your preferred recent window (default 8 hours). Window is configurable per user; the same setting is on your /profile page.

Inputs

NameDescriptionAllowed valuesDefault
Window Dropdown Time range to display (e.g., Last 2 Hours, Last 8 Hours, Last 24 Hours) Preset windows or custom date range Last 8 Hours

Fields & columns

NameDescription
Reverse DNSThe 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

View Recent Scan Results

  1. Open the Recent Scans page — it displays completed and failed scans from your chosen window.
  2. Use the Window dropdown (top-left of the table controls) to switch how far back this view looks. The choice persists across sessions and devices.
  3. Click a scan row to view its results.
  4. Toggle additional columns via the gear icon at the right of the column headers — your visibility choices are remembered per table.

Gotchas

  • If a scan you expect to see isn't here, it may have started outside your window — try widening it, or use Scan History for unbounded search.
  • Auto-refresh runs in the background; the visible row set updates automatically as new scans complete within the window.
  • The window preference is per-user and persists, but each device can have its own preference if you are logged in on multiple machines.
  • 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)

MethodPathDescription
GET /api/scans Fetch scans filtered by status=completed,failed and startedAfter (NOW - window seconds); auto-refresh re-issues this on the configured interval

Related

  • Running Scans — Monitor scans currently executing or pending dispatch
  • Scan History — Search unbounded scan archive for audit and reporting
  • Run Scan — Launch manual scans — view their progress on this page after starting
  • Results — Click a completed scan to view its detailed findings
  • Schedules — Scheduled scans appear on this page when they complete
  • Scan Templates — Templates define what each scan executes
  • Scanners — Scanners execute the scans shown on this page
  • Dashboard — Dashboard widgets pull recent scan data from this page
  • Scanner Jobs — Job progress feeds into the scan status shown here