Real Chromium browser — bounded multi-page discovery

    Cookies and scripts.
    Seen by a real browser.
    Surfaced for review.

    ConsentEase loads your site in a real headless browser, records cookies and scripts present before any consent is given, matches known cookies against a classification database, and presents findings by severity — so you know what to investigate.

    See Sample Report
    consentease.io — scan results

    Scan Complete

    mybusiness.com — illustrative scan result

    Cookies
    14
    72%
    Score
    Issues
    3
    Scripts
    8

    Issues Found

    Pre-consent cookie: _gaHigh
    Missing consent: Meta PixelHigh
    Unclassified cookie: _clckMedium
    Hidden trackers

    You may not know what your site drops.

    • Cookies that fire before consent are a documented risk

      If analytics or advertising cookies are present before a visitor has made a consent choice, that is a finding worth investigating. Most site owners have no visibility into when cookies actually fire.

    • Third-party scripts inject cookies you did not add

      A chat widget, an embedded video, or a pixel can introduce cookies you did not explicitly configure. Each one may require disclosure and a consent basis depending on your jurisdiction.

    • Manual audits go stale the moment a developer ships

      A point-in-time audit is accurate for one moment. When a new script is added or a plugin updates, the audit is no longer current. Rescanning on demand gives you a fresh picture without starting over.

    The diagram above is illustrative. Cookie names, counts, and categories are example data. Actual scan findings depend on your site's configuration and the pages visited during the scan.

    Invisible tracking, made visible

    Illustrative
    Pre-consent cookieUnclassified cookieNecessary cookie

    14 cookies detected. 3 fire before any consent is given — each is flagged as a finding for review. Detection coverage depends on page behavior and scan depth.

    Scanner technology

    How the scanner sees your site.

    Four stages from URL to report: a real browser load, pre-consent recording, database enrichment, and severity-based findings. Coverage is bounded — the scanner visits a limited set of pages rather than an entire site.

    01

    Real browser execution

    Your site is loaded in a headless Chromium browser — not an HTTP crawler. The scanner sees exactly what a visitor's browser sees, including dynamically injected scripts.

    Chromium-based, not HTTP-only
    02

    Pre-consent detection

    The scanner records which cookies and scripts are present before any consent signal is given. These are flagged as findings for review — they are not automatic legal determinations.

    Findings, not violations
    03

    Enrichment and classification

    Each detected cookie is matched against a database of known cookies. Matched cookies receive a provider, purpose, and category (Necessary, Functional, Analytics, or Marketing).

    Known-cookie enrichment
    04

    Severity-based findings

    The report presents findings by severity — High, Medium, or Low. A finding is a signal worth investigating, not a guaranteed compliance failure. Review each with your legal context in mind.

    Review signals, not judgments

    The scanner visits a bounded number of pages per scan, not the entire site. Cookies set after user interaction, behind authentication, or via server-side headers may not be detected. Pre-consent findings are signals for review, not legal determinations.

    What you get

    A scan report built from real browser data.

    The report shows detected cookies by category, pre-consent findings by severity, and any known-cookie enrichment available. Authenticated users can rescan to see what changed since the previous run.

    Scan report — mybusiness.comillustrative
    14Cookies found
    8Scripts detected
    3Findings

    Cookies by category

    Necessary (2)Functional (3)Analytics (5)Marketing (4)

    Findings — review signals

    • HighPre-consent cookie: _ga (Google Analytics)
    • HighMissing consent: Meta Pixel (_fbp)
    • MediumUnclassified cookie: _clck (Microsoft Clarity)

    Findings are review signals, not legal determinations. Scanner coverage is bounded by scan depth and page behavior — not every cookie or script on a site is guaranteed to be detected.

    Headless Chromium execution

    The scanner uses a real browser, not an HTTP crawler, so dynamically injected scripts and lazy-loaded cookies are discoverable.

    Known-cookie enrichment

    Detected cookies are matched against a database of known cookies and classified by provider, purpose, and category where a match exists.

    Pre-consent findings

    Cookies and scripts present before any consent is given are flagged as findings for review. Detection is bounded by scan depth and page behavior.

    Rescan and comparison

    Authenticated users can rescan to see what changed since the previous scan. History and comparison access depend on your plan.

    Scanner scope. The report above is illustrative. Actual scan coverage is bounded — the scanner visits a limited set of pages, not an entire site. Cookies set after user interaction or behind authentication are typically not detected. Pre-consent findings are review signals, not automatic legal violations. PDF export and scheduled rescans are subject to plan access constraints. Free scans are available subject to rate limits; results are not stored indefinitely without an account.

    Feature comparison

    Scan depth, compared.

    Scan method

    ConsentEase
    Headless Chromium browser
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    Manual audit
    Manual browser inspection

    Pre-consent detection

    ConsentEase
    Flagged as review findings
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    Manual audit
    Manual, if you know what to look for

    Cookie enrichment

    ConsentEase
    Known-cookie database matching
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    Manual audit
    Your own knowledge

    Severity-based findings

    ConsentEase
    High, Medium, Low per finding
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    Manual audit
    Depends on auditor

    Rescan and comparison

    ConsentEase
    Available for authenticated users
    Cookiebot
    Check current plan
    CookieYes
    Check current plan
    Manual audit
    Manual comparison

    Shareable report

    ConsentEase
    Link available; access constraints apply
    Cookiebot
    Check current plan
    CookieYes
    Check current plan
    Manual audit
    Screenshots or document

    PDF export

    ConsentEase
    Check current plan
    Cookiebot
    Check current plan
    CookieYes
    Check current plan
    Manual audit
    Not currently provided

    Compliance guarantee

    ConsentEase
    None — findings are review signals
    Cookiebot
    None
    CookieYes
    None
    Manual audit
    Depends on auditor scope

    Neutral, configuration-dependent comparison. Scanner capabilities depend on the vendor's implementation and your plan. Pre-consent findings are signals to investigate, not compliance guarantees. Verify current vendor capabilities before deciding.

    See Full Comparison

    What is your site
    actually dropping?

    Find out in seconds. Enter your domain below and the scanner will show you what cookies and scripts are present before any consent is given.

    Free, no account required. You will be taken to the scanner page.

    Real Chromium browser, not an HTTP crawlerPre-consent findings flagged for reviewKnown-cookie enrichment and classification