Scan status: error

In some cases, you might see an error status next to a performed cookie scan.

Sometimes you may also get such a message: "Oooops! Something went wrong when scanning your website. Please contact our support team:"

First, go to your CookieScript user account > Scans and check how many pages were scanned and how many cookies were found:

Depending on the scanning result, see the possible solutions below:

I. No pages were found during the follow-up (not initial) cookie scan

If only 1 page was scanned, it means your website blocked CookieScript Cookie Scanner. To solve this issue, perform the following steps:

1. Go to your CookieScript user account > Scans, check the checkbox ALWAYS SCAN FROM SAME IP ADDRESS, and press SAVE.

2. Whitelist this IP address on your website: 80.240.129.194

3. Scan your website again.

If no pages were found at all, follow this guide to troubleshoot. 

II. No cookies were found during the follow-up (not initial) cookie scan and no cookies were added to the cookie report

1. If 0 cookies were found, it means that you don't have any cookies implemented on your website. Install the CookieScript Cookie Banner to your website and scan the website again.

2. If too few cookies were found, follow this guide to troubleshoot. 

III. Scanning takes longer than usual

If cookie scanning is not completed within 48 hours, an error status is automatically assigned to the scanning instance. In some cases, automated scanning (like piled-up scanning queue) might take longer than usual. This can be solved by waiting another day for scanning to complete. 

IV. Scanner Stuck in "In Progress" Status

If the website scanner indicates that it is "In Progress" but has not completed the scan and was started more than 48 hours ago, you now have the option to manually stop the scan. Go to the Scans section in your dashboard and click the Stop buttonnext to the ongoing scan.

V. How to whitelist the CookieScript scanner in Cloudflare

If your website uses Cloudflare, its firewall or anti-bot protection might block the CookieScript Cookie Scanner. This can result in scanning errors, only one page being scanned, or too few cookies being detected.

To prevent Cloudflare from blocking the scanner, follow the instructions below.

Step 1. Enable scanning from a fixed IP address

1. Log in to your CookieScript user account.

2. Go to Scans.

3. Enable ALWAYS SCAN FROM SAME IP ADDRESS.

4. Click SAVE.

The CookieScript Cookie Scanner will use the following IP address:

80.240.129.194

Step 2. Allowlist the CookieScript IP address in Cloudflare

1. Log in to your Cloudflare dashboard.

2. Select your website.

3. Navigate to Security > Security rules.

4. Click Create rule > IP access rules.

5. Enter the following details:

   • IP address: 80.240.129.194

   • Action: Allow

   • Zone: Your website

   • Note (optional): CookieScript Scanner

6. Click Create to save the rule.

This allows requests from the CookieScript Scanner IP address to bypass several Cloudflare security checks that could otherwise block the scan.

Step 3. Check Cloudflare anti-bot protection

Cloudflare's bot protection might identify the CookieScript Cookie Scanner as automated traffic and block or challenge its requests.

If you use Super Bot Fight Mode:

You can create a custom rule to exclude the CookieScript Scanner from bot protection.

1. In Cloudflare, navigate to Security > Security rules.

2. Click Create rule > Custom rules.

3. Enter a rule name, such as Allow CookieScript Scanner.

4. Under When incoming requests match, select:

   • Field: IP Source Address

   • Operator: equals

   • Value: 80.240.129.194

5. Under Choose action, select Skip.

6. Select All Super Bot Fight Mode rules.

7. Place the rule before any custom blocking or challenge rules that could affect the scanner.

8. Click Deploy.

You can also use the expression editor:

(ip.src eq 80.240.129.194)

Note: If you already created an IP Access rule with the Allow action in Step 2, it generally bypasses Super Bot Fight Mode, so a separate Skip rule is not normally required. A custom Skip rule is an alternative for creating a more targeted exception.

If you use Bot Fight Mode (Cloudflare Free plan):

Bot Fight Mode does not support exceptions through custom WAF Skip rules. However, an IP Access rule that matches the scanner's IP address can prevent Bot Fight Mode from challenging those requests.

If the scanner continues to be blocked, review your Bot Fight Mode settings under Security > Settings > Bot traffic. You may need to temporarily disable Bot Fight Mode for troubleshooting or use Super Bot Fight Mode for more granular exceptions.

For more information, see Cloudflare's documentation on bot protection exceptions.

VI. Other scanning errors

Sometimes (rarely) there might be an error in the scanner itself. In case none of the issues above match your case, please contact us for further investigation.

You could also look for a possible solutions, related to the scanning of cookies.

The Cookie Scanner allows to rescan your website after 24 hours. If you don't want to wait for 24 hours, you can request to rescan your website via Live Chat.