SERVICES AGREEMENT
This agreement is made between Acme Ltd
and Northwind Studio on 14 August 2026.
3. Fees
The client shall pay a total fee of
USD 24,000.00 on completion.
Northwind Studio
Your file never leaves this tab
Is this document really the one they signed?
Drop in a signed PDF and find out in seconds. You will see every signer, the exact times they signed, and whether a single byte has changed since. Free, no account, and you do not have to be the person who sent it.
Drop a signed PDF hereor browse your files
- Free, and no account
- The file stays in your browser
- Works for documents you didn't send
- Every signer, with timestamps
Why a fingerprint
Change one figure, get a different document
A SHA-256 fingerprint is computed from every byte in the file. It does not change a little when the file changes a little — it changes completely.
SERVICES AGREEMENT
This agreement is made between Acme Ltd
and Northwind Studio on 14 August 2026.
3. Fees
The client shall pay a total fee of
USD 84,000.00 on completion.
Northwind Studio
SHA-256
computing…Matches our record
07e5c3a18f6d4b2907e5c3a18f6d4b2907e5c3a18f6d4b2907e5c3a18f6d4b29
No match
07e5c3a18f6d4b2907e5c3a18f6d4b2907e5c3a18f6d4b2907e5c3a18f6d4b29
62 of 64 characters differ — from a single digit changing in the contract.
Which is why an altered contract cannot quietly pass as the one that was signed. There is nothing to spot by eye and nothing to argue about.
How it works
Drop a file in, get a straight answer
A signed document has to answer two things: is this really the file that was signed, and who signed it? Neither answer depends on us still holding a copy.
01Drop the PDF in
It is read inside your own browser. Only its fingerprint and the certificate already embedded in it are sent to us.
- The document never leaves your device
- No account, and no limit
- Works for documents you did not send
02Two checks, not one
We look for bytes matching a document we finalised, and separately we check our own signature on the certificate the file carries.
- One changed byte breaks the match
- The certificate proves itself without our records
- Retention closing changes nothing
03You get a straight answer
Genuine, genuine but re-saved, self-signed, forged, or unrecognised — with every signer and the exact time they signed.
- Says plainly what it cannot vouch for
- Names every signer, with timestamps
- Certificate readable in any PDF reader
Questions
About verification
What the check proves, and what it does not.
Does my document get uploaded to check it?
No. Your browser reads the PDF and sends two things: its 64-character SHA-256 fingerprint, and the certificate already embedded in the file, so we can check our signature on it. Neither is document content. The PDF itself never leaves your device.
What does “verified” actually prove?
That the file you dropped is byte-for-byte the file Putmysign produced when the document was completed, and that it has not been altered since — not one word, date, figure or signature. We also show who signed it and when.
What if the document was changed after signing?
Any change at all, however small, produces a different fingerprint, so the file will no longer match our record. Because the certificate inside it is signed by us, we can still confirm that the signings it describes really happened — you will be told the evidence stands but that this particular file is a copy, not the original we issued.
Can I verify a document I did not send?
Yes. Verification needs no account and no connection to the original sender. Anyone handed a signed PDF — a bank, a landlord, a counterparty, a court — can check it here in a few seconds.
Can I check it without using this page?
Yes. The signed PDF carries its own certificate page listing every signer, the timestamps, the IP addresses and the SHA-256 of the original file, so the evidence can be read with any PDF reader. This page just confirms the file still matches our record.
Do you need to still have the document on file?
No. Every completed document carries a certificate that we signed, so it proves its own origin even after its retention window has closed and the record is gone. Holding the record only adds the stronger answer — that the file is byte-for-byte the one we produced.
I signed a PDF with the free browser tool — why does it not fully verify?
Because nothing witnessed it. That tool runs entirely in your own browser and never uploads the file, which is the point of it, so there is no record and no signature of ours to check. Verification will say the file was self-signed and show what it claims, but cannot confirm it. Send the document for signature instead if someone else has to rely on it.
Why does it say the file is not recognised?
It carries no certificate and matches no record — so either it was never signed through Putmysign, or it is a copy that was flattened or re-exported by another app, which strips the metadata along with everything else. Verify the original file as it was delivered.
Still stuck? support@putmysign.com
Send documents that verify themselves
Every document completed through Putmysign gets a certificate attached automatically, so anyone you hand it to can run this check without asking you for anything.