Skip to content
THE PLEDGE™Global InitiativeStart learning
New on The Pledge: Daily Inspiration · Daily Research Desk. Free, source-based, and independent.
Document integrity • Honest verification

Check a file. Understand what the result means.

Compare the SHA-256 fingerprint of a signed oath PDF with your private on-device record or a supplied checksum, without uploading your file. This is not public membership verification.

Daily study edition

Understand precisely what a check can establish: discover a carefully sourced question and study exercise, without an account.

Important distinction: This page checks the SHA-256 fingerprint of a PDF you select, entirely in your browser. It can compare it to a fingerprint you provide or a local record saved on this same browser. It cannot confirm official membership, legal identity, authorship, or issuance by an organization. A public server-backed certificate registry is not active.
Step 1 • Select a document

Check your PDF

The file never leaves your browser; no server upload occurs.

Select a PDF to begin. The check runs privately on your device.
Step 2 • Understand results

Document integrity is not membership.

Local match: The file is identical to a copy previously recorded in this browser.

Fingerprint match: The file matches a checksum someone supplied. That person may still have created both the file and checksum.

No local match: This browser has no corresponding record. It does not necessarily mean the document is forged.

QR code opening the publicly accessible PDF integrity checker on this website

This QR opens the checker page. It is not a unique credential, identity proof, or certificate issuer seal.

Open checker

Local certificate references

If you opted to save a fingerprint when signing on this device, it appears here. Records contain only an opaque local reference, the file fingerprint, and the date. No signature image or name is stored by this feature.

Saved on this browser

Loading local records…

Future public verification

A true public registry needs a secure server that issues records, controls who may create or revoke them, and validates each certificate. That is not connected yet; no record on this page should be treated as a publicly authenticated credential.

A cryptographic PDF signature, optional email account, and identity verification are separate mechanisms with different privacy and security implications.