Step 1
Demo
Demo: scan a page with C2PA Signer
A page built to test the extension scan. It contains images and video with different C2PA states, so you can run “Analyze page” and compare the badges and reports.
Step 2
Open this page
Navigate to the demo page in your browser.Step 3
Click “Analyze page”
Run the page scan from the extension popup.Step 4
Compare the badges
See the different trust statuses on each media.Step 5
Open the full report
Inspect the manifest, signature and PKI details.| Media | Expected status | What it means |
|---|---|---|
| Signed trusted sample | Trusted | Valid C2PA + recognized trust chain |
| Signed test certificate | Signed but untrusted | Valid signature, not public trust |
| Modified sample | Invalid | C2PA data exists but validation failed |
| Unsigned sample | No credentials | No C2PA evidence detected |
Test content
Media to inspect on this page
Use these visible samples as scan targets, then compare the badge and the full report with the expected result below each media item.
Trusted
Media with readable Content Credentials
Expected report: readable provenance, verifiable signature and integrity details when the trust chain is recognized.
Signed but untrusted
Generated or edited signed image
Expected report: provenance is present, then the report helps qualify the certificate, issuer and trust status.
No credentials
Video without integrated provenance
Expected report: no integrated C2PA provenance is detected for this common open-web video case.
No credentials
Image without embedded C2PA information
Expected report: no usable provenance proof is found in the file. This does not prove that the content is fake.
Invalid
Altered content case
If a signed media file is modified without updating its manifest, cryptographic integrity no longer matches the observed file. The extension should show this as a broken or invalid provenance case when such a file is present.