Verification is what separates a trustworthy e-signature from a simple image paste. Anyone can insert a picture of a signature into a PDF — but can they prove it wasn't added yesterday, or that the document hasn't been modified since signing? SignForge embeds a comprehensive verification system into every signed document.
Global · Enacted Ongoing
QR code embedded on every signed document for instant verification
SHA-256 hash matching confirms the document hasn't been modified since signing
ECDSA P-256 digital signature proves the verification record's integrity
Verification JSON embedded as attachment inside the signed PDF
Public verification page — no account or login required
Verification records are permanent — they survive document deletion
Verification is what separates a trustworthy e-signature from a simple image paste. Anyone can insert a picture of a signature into a PDF — but can they prove it wasn't added yesterday, or that the document hasn't been modified since signing? SignForge embeds a comprehensive verification system into every signed document. Each signed PDF contains a QR code in the bottom-right corner that links to a public verification page. The verification record includes the document's SHA-256 hash, the signer's identity, timestamps, and an ECDSA P-256 digital signature that cryptographically proves the record's integrity. Verification records are stored independently from documents — they survive even if the original document is deleted. Anyone can verify a document by scanning the QR code, entering the verification code, or uploading the PDF to our verification page. No account is required.
These are the facts we capture and store for every signature. Document integrity verification sets the requirements above — whether what we record satisfies them for a given transaction is a legal question that depends on the circumstances.
Every signed document gets a unique verification code (sf_ + 12 characters)
QR code placed on the last page of every signed PDF (1.5cm, bottom-right)
signforge_proof.html embedded as self-verifying proof document with W3C VC, JAdES JWS, Merkle proof, and ECDSA signatures
Public verification at /verify — enter code or upload PDF, no account needed
Verification records stored separately — survive cascade deletes
Audit certificate includes verification section with code and URL
TLS 1.3 + SHA-256
Cryptographic proof
Append-only, immutable
Certified infrastructure
Three ways: (1) Scan the QR code on the last page of the signed PDF, (2) Enter the verification code (starting with 'sf_') at signforge.io/verify, or (3) Upload the signed PDF to the verification page. All methods are free and require no account.
Verification checks three things: (1) The SHA-256 hash of the uploaded document matches the hash recorded at signing time, (2) The ECDSA P-256 digital signature on the verification record is valid, and (3) The signer details and timestamps match the audit trail.
Yes. The verification page is completely public — anyone with the QR code, verification code, or the signed PDF can verify the document's authenticity without creating an account or logging in.
General information — not legal advice
This page summarizes electronic signature legislation drawn from primary legal sources and international bodies including UNCITRAL and UNCTAD. It is not legal advice and creates no solicitor–client or attorney–client relationship. Laws change, and how they apply depends on the transaction, the parties, and the document type. Before relying on electronic signatures for a regulated, high-value, or cross-border transaction — or for any document type listed as excluded — take advice from qualified counsel in the jurisdiction whose law governs that transaction. That is a separate question from the governing law of your agreement with SignForge, which is set out in our Terms of Service.
Last reviewed: 10 August 2026
Legally binding e-signatures with 256-bit encryption, cryptographic verification, and an immutable audit trail. Free forever.
Get started freeNo credit card required.