Content Credentials
Every digitisation here can be cryptographically verified.
When we digitise a primary source we record how, when and with what it was captured, then seal that record with a tamper-evident digital signature. Anyone can check, on any device, that what they are looking at has not been altered since it was created. This is the open C2PA standard for content provenance and authenticity - the same approach used to tell real media from fakes.
- Most recently signed
- 2026-06-10 18:11:33.000
- Issuing key(s)
-
127596d1e0e37e7f×3
Content credentials are sealed with an Ed25519 signature and re-checked live on every view.
Have a reference for a specific record? Check its authenticity directly.
Tip: append a record permalink to /verify/, or use /verify/id/ followed by a numeric record id.
Checking one file? Use /verify/ followed by its file (digital object) id to see that file's content-credentials chain and an embeddable verify badge.
Have a file from anywhere? Check its content credentials by uploading it.
New to content credentials? Read what they are and how to check.
1Capture
At digitisation we record who captured the source, when, and on what device and software.
2Sign
That record is sealed with an Ed25519 digital signature over the exact captured content.
3Embed
The signed credentials are embedded in the file or stored alongside it as a sidecar, following C2PA.
4Verify
On every view the signature is re-checked live - nothing is cached - so tampering is caught immediately.
Open standard, no vendor lock-in: anyone can independently verify a Heratio content credential using the public C2PA tooling.