Practical answers about scan scope and plan limits

CertScore.ai scans public website pages for accessibility signals, privacy and cookie-consent behavior, tracker activity, policy-page presence, disclosure gaps, and policy-to-behavior contradictions that can be supported by retained evidence.

Findings describe evidence recorded during a public website scan. They reflect the pages, time, region, and coverage of that visit, and should be checked against the retained evidence. They are not legal or formal accessibility determinations.

A website can show different content, consent choices, cookies, and requests by location or over time. Use the report's scan timestamp and region when reviewing a finding; a later visit or a visit from another region may behave differently.

No. The MVP scans public websites only. Logged-in, private, or staging-only pages are outside the current scan scope.

CertScore.ai stores structured scan metadata, derived signals, timestamps, change history, evidence URLs, and limited policy or disclosure excerpts when needed to support analysis and review. It is not positioned as a full-page archive of raw site content.

Homepage previews return quickly. Larger scans usually take a few minutes depending on site responsiveness, page count, and the selected scan scope.

Plans are based on page scans per month. Starter includes 50 page scans per month, Pro includes 500 page scans per month, and Custom plans support higher-volume workflows.

After signup, you can save websites, run broader scans, review structured findings and retained evidence in the app, and track changes over time.

No. CertScore.ai surfaces observable signals and supported findings. Review and remediation still need to be handled by your team.

On eligible sites, CertScore.ai can attempt one bounded first-layer Reject action in a separate browser session. The report distinguishes a completed click from a confirmed refusal and retains bounded after-click observations when available. Confirmed post-refusal findings require their own verified evidence; a separately verified Reject-click tracking signal may support review even if consent registration remains unconfirmed. Incomplete or unverifiable observations remain limited coverage.

It means the available evidence did not resolve the choice path—for example, the control inspection was incomplete, the interface was unsupported, the action was unverifiable, or the observation timed out or went stale. A completed inspection that finds no matching control can instead make that action not applicable. Limited coverage is explicit and is not a pass; separately verified Reject-click tracking can still support its own review signal.

Scan requests are paced at one request every 1 minute. Manual re-scans and scheduled monitoring consume scan credits; high-frequency monitoring and batch scanning are handled as custom higher-volume setups.

Run another scan. CertScore.ai compares each completed scan to the previous one so you can see added, removed, and changed signals over time.

No. CertScore.ai scans public pages for observable website signals and change history. It does not provide legal advice or certification.

No. CertScore.ai records observable website behavior and supporting evidence from a point-in-time scan. Its findings help people review possible issues; they do not certify a site or determine legal compliance.