You'll need
A project with at least one completed report
Time
~1 min to start, then the scan duration
Plan
Re-scans count toward your plan — see /pricing
Reports are point-in-time. The moment you fix a finding, publish a new legal page, or ship a feature, the report on screen is out of date. Re-running the scan refreshes it — and because Wolfix stores each run separately, you can see exactly what your change closed.
Open the project you changed
From your dashboard, open the project whose report you want to refresh. The current report shows the last scan's findings — your goal is to replace it with a fresh read.
Start a new scan
Click Re-scan (or Start scan if no scan is running). Wolfix runs the pipeline again against your current project state. Choose the same mode you need: a quick scan to confirm a document or code fix, or a deep scan if your change touched DNS, cookies, or providers.
Match the mode to the fix
Fixed a privacy policy or a meta tag? A quick scan confirms it. Changed an SPF record or added a cookie banner? Use a deep scan so the dynamic and DNS checks actually run.
Wait for the run to finish
The scan runs in the background — a quick scan finishes in seconds, a deep scan in up to a minute or two. You can leave the page; the new report appears in your dashboard when the run completes.
Compare before and after
Open the new report. Because each run is stored separately, you can compare it against the previous one: the finding you fixed should move out of Blockers or Risks and into Covered. Anything still open stayed open — which tells you the fix did not land the way you expected.
Confirm the gap is closed
A finding is only resolved when it shows as Covered in a fresh scan. If a fix you applied still appears as a Blocker or Risk, the change may not be live yet — check that your deploy finished, your DNS propagated, or your hosted page actually published before re-scanning again.
Verify against the live project
Wolfix scans your live URL and current code, not your local draft. A change that only exists in a preview or an unpushed branch will not show up until it is deployed and publicly reachable.
You just did
Your report is back in sync
- Re-ran the scan against your current project state
- Picked the scan mode that matched your change
- Compared the new report against the previous run
- Confirmed the finding moved into Covered