Running a scan
A scan is the quickest way to see exactly what's running on your website right now.
Before you start
Your website needs to be added and verified. If you haven't done that yet, see Adding a website and Verifying your website.
You'll need an Owner or Admin role to start a scan.
If your website sits behind a firewall or bot-protection, make sure these scanner IPs are allowed before you start:
187.127.178.59
72.62.147.130
Otherwise the scan may fail because the scanner can't reach your website. See Scan failed or stuck for details.
Open the Scanner page
Sign in, open your project, and go to Cookies → Scanner.
You'll see a list of past scans, with the most recent on top.
Start the scan
Click Start Scan in the top right. A short confirmation dialog opens. Click Start Scan to confirm.
A new row appears at the top of the list with the status In Progress.
While the scan runs
The page refreshes the in-progress scan automatically every few seconds. You can leave the page open and watch it, or come back later.
A small website usually finishes within a few minutes. Larger sites take longer because there are more pages to visit.
When the scan finishes
The status changes to Completed and the row fills in:
Total Unique Cookies. How many distinct cookies were found across the whole website.
Total Pages. How many pages were scanned.
Created By. The teammate who started the scan.
Click anywhere on the row to open the scan details.
If a scan fails
Sometimes a scan ends with the status Failed. This usually means the scanner couldn't reach the website, or the website returned an error during the scan.
Try starting a new scan. If it fails again, see Scan failed or stuck or contact support.
Filtering past scans
The dropdown at the top of the Scanner page filters the list by status: All Status, In Progress, Failed, or Completed. Useful when you want to find a specific scan in a long history.