Comparing Scans

The scan comparison feature lets you see what changed between two scans — helpful for verifying that fixes were effective or catching new regressions.

How to Compare

1. Navigate to Scans → Compare Scans (or access it from the scans page).
2. Select Scan A (baseline) — typically the older scan.
3. Select Scan B (latest) — typically the newer scan.
4. Click Compare.

Both dropdowns show all your completed scans in the format:

#ID — target_url (date)

Understanding the Results

Score Comparison

Three columns show the score change at a glance:

Column	Description
Scan A	Score gauge for the baseline scan
Score Change	The difference (green if improved, red if worse)
Scan B	Score gauge for the latest scan

New Findings

Findings that appear in Scan B but not in Scan A — these are new vulnerabilities introduced since the baseline. Displayed as red-tinted cards with severity and title.

Resolved Findings

Findings that were in Scan A but not in Scan B — these are vulnerabilities you fixed. Displayed as green-tinted cards with severity and strikethrough title.

Tips

Track your remediation progress

Run a scan, fix the reported issues, then run a second scan and compare the two. Resolved findings confirm your fixes are working.

Same domain for meaningful comparisons

For the most meaningful results, compare scans of the same domain and path with the same modules enabled.