Exact document file
The approved PDF, DOCX, XLSX, PPTX, PNG, JPEG or text file is used to calculate its SHA-256 fingerprint.
Document seals let a recipient compare a local copy with the approved fingerprint without retaining the uploaded comparison file. Choose integrity-only, verified issuer or a high-security approved issuance workflow.
Exact-file fingerprintA SHA-256 fingerprint identifies the exact approved file rather than only its filename.
Private comparisonRecipients can compare a copy without the verification service retaining that comparison upload.
Document authentication is based on the exact file fingerprint. Issuer identity and approval workflow depend on the assurance level selected.
The approved PDF, DOCX, XLSX, PPTX, PNG, JPEG or text file is used to calculate its SHA-256 fingerprint.
Title, category, reference and issue information help a recipient identify the intended record.
Verified Issuer and High Security products also connect the fingerprint to an approved organization.
A SHA-256 fingerprint identifies the exact approved file rather than only its filename.
Recipients can compare a copy without the verification service retaining that comparison upload.
Add verified organization identity when recipients need to know who issued the document.
Support manual, automatic, trusted-organization and reseller/API approval paths.
Open any seal to see its exact checks, requirements, availability, limitations and current design.
Confirms that an uploaded document exactly matches the approved SHA-256 fingerprint.
See this seal and what it verifies →Confirms the exact document fingerprint and the verified identity of its issuer.
See this seal and what it verifies →High-security document fingerprint authentication issued through an approved workflow.
See this seal and what it verifies →Product requirements can vary, but every category follows a clear path from submitted information to a public status record.
Choose integrity, verified issuer or High Security authentication.
The approved document is fingerprinted with SHA-256; the temporary file is not retained.
Place the seal or verification link with the document so recipients can compare a copy.
The live certificate remains the source of truth. These placements make it easier for a visitor to find and open it.
Place the seal image or verification link on a cover, certificate or final information page.
Show verification beside the exact file offered to the recipient.
List issued documents with links to their live records and current status.
Include the verification link when sending a certificate, report or formal document.
Every seal page also explains its exact checks, requirements and important limitations.
No. The recipient upload is fingerprinted for comparison and the temporary file is not retained by the verification workflow.
Any byte-level change creates a different SHA-256 fingerprint. The comparison confirms an exact file match, not visual similarity.
No. It confirms the exact fingerprint and issuer information shown; it does not decide whether the content is legally enforceable or factually correct.