Skip to content

Re-scan · after a Go

No negative finding. The re-scan checks the same address again later.

What we can offer is keeping an eye on whether it stays that way. An MVP does not degrade on the day of the scan, but over the next twenty deploys.

Set up the re-scan

The confirmation and later the alert go to this address. Please use a work address — the alert should land where someone can act on it.

No newsletter. One email when things get worse — otherwise none. Unsubscribe at any time via the link in every email.

Why this is not nothing

The most common route to an open database is not a bad first attempt, but a change weeks later that nobody reviewed. That is exactly what the re-scan is for.

How often this happens

Every 7 days, up to 52 scheduled re-scans per year, including a runtime check in the browser. On request also one after every deploy, at most one per 30 minutes. The cadence is short, the mail is not: you hear from us only when a run finds something new — otherwise not at all.

Verified domains only

We set up the re-scan only for domains whose operation is proven — via DNS record, file or meta tag. Otherwise someone could have foreign systems scanned indefinitely.