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 reflect automated analysis of public website signals under the tested scan context. They are designed for human and agentic review and monitoring, not as a legal or formal accessibility determination.

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, yes. CertScore.ai performs one bounded refusal in its own browser session, confirms a refusal-state transition, and retains the requests, cookies, storage, and consent signals that follow. Only activity anchored after confirmation counts, so an already in-flight request is not attributed to the refusal. This is evidence relevant to GDPR/ePrivacy review, not a compliance determination.

It means the interaction could not be completed or confirmed—for example, there was no identifiable control, the interface was unsupported, the action was unverifiable, or the observation timed out or went stale. Limited coverage is explicit, score-neutral, and not a pass. It means the question was not answered.

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.