# Check again

Confirm a fix worked with a free re-read of your public records or a new scan, and see what changed since last time.

There are two ways to confirm a fix. Use the one that matches what you changed.

## Changed a DNS or email record

On an issue about your public records, choose **Re-read this record**. Lockpick re-reads your public DNS records, the certificate log and domain registration, and tells you whether the issue is fixed.

* It sends no requests to your site.
* It's free and doesn't use a scan.
* You can use it once a minute for each scan.
* It updates that issue only. Your grade changes on your next full scan.

> **Good to know**
>
> DNS changes can take a while to spread. If the answer is "Could not
> confirm", wait a few minutes and try again.

## Changed your site

Choose **Check again** on your site's page. It runs a new scan of the same kind, so it uses one scan from your allowance, and the original scan and its evidence are kept.

When it finishes, the report compares the two scans.

| What you see | What it means                                                      |
| ------------ | ------------------------------------------------------------------ |
| New          | New in this scan                                                   |
| Still open   | Found again in this scan                                           |
| Fixed        | This scan read the same page or record again and it was gone       |
| Inconclusive | This scan could not tell either way, so it is not counted as fixed |

[How we rate findings](/docs/security/how-we-rate-findings) explains what each state can and cannot prove.

## Script changes between Deep scans

When you run Deep again, the report also has a **Script changes** section. It compares the outside scripts your pages declare, on the pages both scans read, and flags a **New script provider** or an **Integrity hash removed**. If you meant the change, for example a chat widget you added, a site manager can choose **This change is expected**, then **Mark as expected**, and auto-checks stop alerting on it. **Undo** brings the alert back. A Deep auto-check that finds a change you haven't marked rings the bell and lists it in its email.

It only covers the script tags your public pages declare. Packages bundled into your own code aren't listed, and a new provider on its own is never proof that something was compromised.

## Record what you fixed

Open a finding in a scan result and choose **I fixed this** to keep a note of what you changed. The site's **Repairs** tab lists every repair you recorded and what later scans found, from **Waiting for a follow-up scan** to **Not seen on revisit**, **Still present**, **Inconclusive** or **Came back**. Your note stays your own statement. Only a later comparable scan that reads the same place again changes the status. Recording a repair needs a site manager, and you can download the history as JSON or CSV.

## Let Lockpick check for you

Instead of remembering to check again, turn on **Auto-check this site** on the **Auto-check** tab. Lockpick scans your site every week and emails you what was fixed, what is new and what is still open.