Open navigation menu
What a CertScore evidence report gives your team.
This sample shows the shape of a review packet: automated public-web observations, retained evidence, and clear next-step signals for privacy, product, agency, or security review.
Sample content is illustrative. CertScore surfaces observations for review and does not provide legal advice, certification, or compliance determinations.
Executive snapshot
Consent timing
Pre-choice activity observed
Vendor footprint
12 third-party hosts
Reject path
Changed some behavior
Review priority
Needs follow-up
Signals a buyer can review without rerunning a manual audit.
CertScore reports are designed to make the observed browser behavior easy to triage, reproduce, and discuss with implementation owners.
| Signal | Observation | Evidence retained |
|---|---|---|
| Tracking before consent | Marketing and analytics requests appeared before a consent choice interaction. | First request at 420ms after page load; example hosts include tag-manager.example and ads.example. |
| Reject behavior | Rejecting the banner reduced some requests, but several third-party calls still appeared afterward. | After-reject scan retained collection endpoints from two observed vendor domains. |
| Cookie and storage activity | Non-essential-looking cookies and local storage keys were observed during the page session. | Cookie names and storage keys are grouped by category when the scanner has enough context. |
| Disclosure consistency | The privacy text described analytics and advertising tooling, but observed runtime behavior should be reviewed against current configuration. | Policy snippets are retained with source URLs for human review. |
| Accessibility signals | Automated checks found several page-level accessibility signals that may deserve product review. | Examples include missing alt text, heading-order issues, or contrast warnings where observed. |
The same report becomes more useful over time.
One scan answers what happened during one run. Monitoring helps teams see whether the public behavior changed after tag updates, consent changes, vendor rollouts, or site releases.
Ready to see your own public-site signals?
Start with a trial scan, then use pricing to choose a scoped review or monitoring path.