Here are the TOP 5 reasons or our scanner returning 0 cookies:

  1. The website was not live when the scanner started
  2. Domain has just been added to your consent solution
  3. The Cookie Information scanner IP is being blocked
  4. The website contains redirects
  5. The wrong domain is whitelisted
  6. The scanner is looping
  7. Consent Pop-up not visible on the website
  8. Still not sure

Once the domain is added to our platform our scanner will immediately be added to our scanner queue and a scan will follow shortly after. The scan can take up to 24 hours to finish, depending on the domain size. In most cases, it takes between 2 - 4 hours.

Our scanner is set up to emulate a real user that goes through the website and gets cookies set in their device.

Sometimes the scanner will send a high amount of requests to the website's servers. This can in some cases be seen by the server as an attack, like DDOS.

In these cases, the server may block our scanners.

Make sure that the website firewall is not blocking our scanners' IP address that is associated with


The scanner uses a certain `User-Agent` header, which allows anyone to identify the traffic that is coming from us
The header is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36(KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 CookieInformationScanner

So it can also be possible to whitelist us by user-agent header:


The website contains redirects

A redirect is a widely used practice, but in some small cases, a redirect can result in our scanner either looping or timing out.

If the solution is set up to scan a specific domain, but this domain is being redirected to another, this will also stop the scan.

The wrong domain is whitelisted

If the domain provided for the consent solution is not the same as the domain/website you have implemented the policy on that will also result in an empty policy or a 404 error in the console.


Please check the URL for the solution is the same as the website you want to use the solution on, in Cookie Information Platform at

The scanner is looping

We sometimes a web-widget on a website resulting in our scanner ending up in an endless loop. Eg. A calendar-functions with clickable links that auto-generate new links.


Turn off or remove the web-widget during the scanning process.

If our popup-script is implemented on the website the scanner will click the accept-button to by-pass the cookie control SDK.

But if the consent pop-up is not visible in the browser window then the scanner can not click the accept-button, and the scanner will timeout.


Make sure the consent pop-up is implemented on your website. See the guide to implement the consent pop-up.

Still not sure

Please contact our support team, so we can help you

Did this answer your question?