Check Bookmarks… — from the ▦ toolbar dropdown, ☰ menu → Bookmarks, or the button of the same name inside Manage bookmarks… — checks every saved bookmark's link in the background and lists only the ones that failed, with a plain-language reason for each.

How a check works

Each bookmark is tried with a lightweight HEAD request first; if that fails, it's retried once with a full GET before being counted as broken. Reasons shown include HTTP errors, DNS resolution failures, connection errors, timeouts, SSL/certificate errors, and redirect loops — TLS certificate verification is never turned off to get a result. A bookmark whose address isn't even a valid http/https link is listed too, but without implying a request was ever sent for it.

Rate-limited or overloaded sites

If a server answers with 429 or 503, Vodou backs off and retries the same request — honoring the server's own Retry-After header when it sends one, capped at a minute — for up to three attempts before giving up. This keeps several bookmarks on the same busy or rate-limited host from being reported broken just because they were all checked at once.

Following a scan

A progress bar shows how many bookmarks have been checked so far (for example 9 / 20 checked (45%)). When the scan finishes it reads Scan complete, with how many bookmarks were checked and how many failed, and the window flashes in the taskbar if you've switched to something else.

While a scan is running, Stop scan is the only button you can use; the others are greyed out. Once the scan finishes, or you stop it, they come back and Stop scan greys out instead.

Timeout and concurrency

Two settings in the dialog control the check: how long to wait per request (8 seconds by default) and how many checks run at the same time (16 by default). Both can be adjusted before starting a check.

Nothing is ever deleted automatically. Review the failed list, use Select all or check entries individually, then Delete Selected… — which still asks you to confirm. A failure here doesn't always mean a page is gone for good: a temporary outage, an expired certificate, or a login wall all show up the same way, so the reason column is worth reading before removing anything.

This check makes plain HTTP requests only — it doesn't need Ollama or any AI model.