01
Bring the record
Open its verification link or use the verification tools to submit the supported record or proof.
Platform
Cryptographic document verification
See who signed a record, whether its content changed, and whether it is still active.
Records & verification
Verification, explained.
A shared record should come with a way to check it. Truthlocks brings the signature, issuer, and current status together so you can review the evidence before relying on it.
A valid signature confirms source and integrity. It does not independently establish that every claim made by the issuer is true.
Platform
Using verification
02
Run the checks
The system checks signatures, content integrity, and the available status information.
03
Read the result
Use the result alongside your own checks on the issuer and the claim.
Details and limitations
Verification: inputs, outputs and limits
What you bring and what you receive
Bring a supported record identifier, public proof link or compatible proof bundle. If you want to compare a document, keep the exact file you received: its name, logo and appearance cannot establish that it matches the signed version. A hash-only record does not contain a recoverable copy of your document.
Read the checks separately: signature, content match, issuer information and current status answer different questions. A successful signature check binds particular signed bytes to a key. It does not establish that the issuer is accredited or that the statement is factually correct.
Operating boundaries and a first test
Recipients can inspect public proofs in Verify without an account. Application teams use Console to configure their integration. Treat unavailable evidence as an unresolved check; do not turn a timeout or missing key into a valid result.
Check one known signed record, then compare a one-character change or an altered file. Confirm that your interface distinguishes a mismatch from a revoked record and an unavailable service. Keep the original record unchanged during testing.
Watch the idea · 32 seconds
Same filename. Different file.
A familiar logo is not an integrity check. See why the exact file and its signed evidence matter.
AI presenter and illustrative scenes. This is a product explanation, not a live verification result or customer testimonial.
Understand record verificationRead the explanation without video
Two files can have the same name and look alike, but contain different information. Compare the file you received against the recorded fingerprint and inspect the available signature evidence. A match supports a content-integrity check. It does not make every statement in the document true. Check the source, current status and context before relying on it.