Checking again, and how to know a fix worked
How Lockpick confirms a fix, what "fixed" means in a report, and how auto-checks catch problems that come back.
Fixing something and knowing it's fixed are two different things. A setting can be saved in the wrong place, a change can be waiting to publish, or a cache can keep serving the old version.
Check again
Once your change is live, choose Check again on your site. It runs a new scan of the same kind, which uses one scan, and compares itself with the last one. It lists what was fixed, what's new and what's still open.
Re-read this record
A thing to fix that lives in your public records, such as a DNS or email setting, also has a Re-read this record button. It reads that record again right away, for free, and tells you whether the problem is still there. It sends nothing to your site and uses no scan.
What "fixed" means
A problem counts as fixed when a scan looked again and no longer saw it. If a scan couldn't look, for example because the site was down or blocked the check, the problem isn't counted as fixed. It's marked as not checked this time, so a clean result never hides a gap.
Catch it if it comes back
Fixes get undone. A new deploy restores an old setting, or a new page adds a script from somewhere else. Auto-checks scan your site every week and email you what changed, so a problem that comes back doesn't go unnoticed.
Was this helpful?