SHA-256 checksums for every Prinn installer. Verify your download before running it.
Every installer is published with its SHA-256 hash. Verify a download before running it. Compare the hash below against the file you downloaded.
macOS and Linux: run shasum -a 256 <file> in a terminal. Windows: run Get-FileHash <file> -Algorithm SHA256 in PowerShell.
If the hash printed by the command matches the one listed, the file you have is byte-for-byte the one we published: not corrupted in transit and not swapped by a mirror, a proxy, or anything else between us and you.
A SHA-256 checksum is a 64-character fingerprint computed from the exact bytes of a file. Change a single byte anywhere in an installer and the fingerprint changes completely. Comparing the fingerprint of your download against the value published here confirms that the file on your disk is identical to the file we built, whatever route it took to reach you.
Prinn inspects your traffic and guards your secrets, so its installer is exactly the kind of file worth tampering with. Verifying the checksum takes seconds and removes that risk: you know the code you are about to run is the code we shipped, not something altered on a mirror, a shared drive, or a compromised network.
Do not run the installer. A mismatch means the file is not the one we published. The cause is often mundane, such as a download that was cut short, but treat the file as untrusted either way. Delete it, download a fresh copy directly from prinn.ai, and verify again. If the second download still does not match, stop and contact support so we can investigate.
macOS builds are also code-signed with our Apple Developer ID and notarized by Apple, so Gatekeeper verifies the signature before the app first opens. That check is independent of this page; comparing the SHA-256 hash yourself adds a second confirmation that does not rely on any single system.