Check who signed a Windows program
Drop an .exe, .dll or .sys. See whether it is signed, by whom, whether it has changed since, and whether the timestamp holds up. It works on a Mac or Linux, and nothing is uploaded.
The program
Drop a Windows .exe, .dll or .sys file here, or choose it. It is read in this tab.
What the signature says
How it works
What a signed program is
Windows programs are signed with Authenticode: the publisher hashes the file, signs the hash with the key in their code-signing certificate, and stores the signature at the end of the .exe, .dll or .sys. Windows reads it to show the publisher's name in the prompt before a program runs, and in the Digital Signatures tab of the file's properties. On a Mac, on Linux or on a Chromebook there is no such tab, and the usual advice is to upload the file to a scanning site.
What is checked
- That the program has not changed. The file is hashed the way Windows hashes it, leaving out only the checksum and the signature itself, and compared with the hash the signature records. One changed byte anywhere in the program shows.
- That the publisher signed it. The signature is checked against the publisher's certificate with your browser's own cryptography, and the certificate has to be one issued for signing code.
- When it was signed. A timestamp from a timestamping service proves the file was signed while the certificate was valid, which is why a signature can outlive the certificate. Both kinds are checked: the RFC 3161 timestamps STAMP reads, and the older countersignatures.
- Every signature on it. Many publishers sign twice, with SHA-1 for old Windows and SHA-256 for new; the second signature is nested inside the first and is checked the same way.
- Things added afterwards. Data appended after the signature, or hidden inside the signature block, is outside what the signature covers, and is named.
What it does not do
It does not decide whether Windows trusts the publisher's certificate authority, which depends on the roots installed on the machine; it names the root instead. It does not check whether the certificate has been revoked, which would mean asking the certificate authority over the network. It does not run or scan the program: a validly signed program can still be harmful, and the signature only tells you who is responsible for it. It reads .exe, .dll and .sys files; Windows Installer (.msi) and .cab files are signed differently and are not read yet.
Questions people ask about VOUCH
How do I check the digital signature of an .exe without Windows?
Drop the .exe on this page. VOUCH reads its Authenticode signature in the browser, on a Mac, Linux or a Chromebook, and says who signed it, whether the file has changed since, and whether the timestamp holds up. The file is not uploaded.
How do I verify an installer is really from the publisher?
Check that it is signed, that the signature is valid, and that the publisher named is the company you expect. A valid signature by a different or unfamiliar name is the thing to stop at. VOUCH shows the name the certificate carries, which is the one Windows shows.
What does it mean if a signature is valid but the certificate has expired?
If the signature has a timestamp from while the certificate was valid, it is fine: Windows accepts it, and that is what timestamps are for. Without a timestamp, Windows stops accepting the signature once the certificate expires.
Does a valid signature mean a program is safe?
No. It means the program has not changed since it was signed and says who signed it. Malware has been signed with stolen and with legitimately bought certificates. The signature tells you who is responsible, not what the program does.
Why does the file have two signatures?
Many publishers sign twice, once with SHA-1 for older versions of Windows and once with SHA-256 for newer ones. The second is nested inside the first. VOUCH checks both.
Is the file uploaded?
No. The file is read and hashed in your browser. VOUCH shows the file’s SHA-256, which can be searched on scanning sites in place of the file itself.
Doing this often? The OBSCURA Sovereign Suite signs your own releases and checks every file in a batch before it is opened. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.