Verify a security report
Drop a PDF to confirm it was signed by Hal and has not been modified since. Everything happens in your browser: the document is never uploaded.
Or drag the PDF anywhere onto this panel. It is read in your browser and never uploaded.
This check runs in your browser
Which is the point: your document is never uploaded, so nothing about it reaches us. It does mean JavaScript has to be on for this page. With it off, a full PDF reader such as Adobe Acrobat will still tell you whether the document was edited after signing. What that reader cannot tell you is that the signer was Hal, which is what this page is for. Report Verification explains the difference.
What this proves, and what it doesn't
Every report Hal writes is a signed PDF. A pass here means two things, and only these two: the report came from Hal, and not one character of it has changed since Hal signed it. It says nothing about whether the conclusion in the report is correct. That is a separate question, and the reasoning behind it is on the page itself.
Why you don't have to take our word for it
A report you can only authenticate by asking the vendor is a report your client's auditor has to take on faith. So the thing this page checks against is not held by us: Hal's signing fingerprint is published as a public DNS record, and the check compares the certificate inside your document against that record.
You can read the same record yourself, without visiting this page:
dig +short TXT _pdf-signing.runhal.comIf the fingerprint in that record matches the one shown above after a check, the document is Hal's. If we ever rotate the signing key, the record changes and every reader sees the new value at the same time.