Evidence scope

A certificate evidences that a file producing the listed SHA-1, SHA-256 and SHA-512 digests existed no later than the sealed timestamp, and that the declaration recorded was submitted by the account holder at that time.

Integrity: if a copy of the file reproduces the same digests, it is byte-identical to the sealed file. If any digest differs, the copy has changed.

Timing: the moment of sealing is attested by the timestamp source named on the certificate. The timestamp source is structured for RFC 3161 authorities.

Limits: a certificate does not establish authorship, ownership, originality or novelty; it is not a public or legal registration; it does not verify the truth of the declaration; and it does not guarantee any outcome before a court, platform or arbitrator.

How it is normally used: as one dated, tamper-evident element among your own records — briefs, contracts, project files and correspondence.