Scan stopped

Why it matters

A firewall that puts unknown visitors on a waiting screen stops a lot of bots. It also stops Snaglist, so the result is incomplete. Checks that did run are still in the result.

How Snaglist checks it

This is part of the security check, a separate check next to the crawl, in Studio and Bureau, and only on a site you have verified. Snaglist only looks at what any visitor can see from outside. It never logs in, guesses no passwords and sends no attacks. It recognises the waiting screens and block pages of common firewalls, such as Imunify360, Cloudflare, SiteGround, Wordfence and Sucuri, and stops right away.

Common causes

• A strict firewall at the host
• Several scans or crawls shortly after each other
• A security plugin that blocks unknown user agents

How to fix it

1. Run the security check again later. Such a waiting screen usually disappears within an hour.
2. Ask the host to allow the user agent Snaglist.
3. Allow Snaglist in the security plugin.

How it shows in the report

In the report for your client this appears under the heading "Your site's firewall stopped the scan". When everything is in order, the report says: "The scan could run all checks".