Runs entirely in your browser

Verify a certificate

Anyone holding a ProofWipe certificate and its wipe log (an auditor, a buyer, a downstream ITAD partner) can confirm the pair is unaltered since issuance. Your files never leave this page: the hash is recomputed locally with your browser’s own cryptography, and nothing is uploaded or stored.

Sample certificate: verify it yourself

No certificate handy? Download this sample pair (placeholder operator and device data, produced by the real engine: NVMe firmware Purge, 100% read-back verified) and load both files below: it passes. Then change any byte of the log and watch it fail.

Certificate (HTML)Wipe log View the PDF

Check a certificate + wipe log

Select the HTML certificate and the …-wipe-log.txt file saved beside it.

Certificate (.html)

Wipe log (…-wipe-log.txt)

Manual mode

For older certificates without a machine-readable block: paste the SHA-256 printed on the certificate and select the log file.

SHA-256 from the certificate

Wipe log file

What a match proves, and what it doesn’t

The wipe log is byte-for-byte the one the certificate’s SHA-256 was computed over: the record is unaltered since issuance
The outcome, serial, and method shown as verified are read from the hash-verified log itself, including partial or cancelled wipes, so altering any of them breaks the hash. A certificate whose summary disagrees with its own log is reported as a FAIL
It does not prove who issued the certificate, or that a wipe physically occurred on the device. An offline, no-phone-home tool has no honest way to prove origin, so this page doesn’t claim to. Provenance comes from your chain of custody.

Prefer to verify offline?

The same check works with standard tools and no browser at all. The wipe-log file’s raw bytes are exactly what the certificate’s hash covers, so recompute and compare:

Get-FileHash '.\ProofWipe-XXXXXXXX-…-wipe-log.txt' -Algorithm SHA256

On Linux/macOS: sha256sum the same file. If the output matches the “Log SHA-256 (tamper evidence)” line on the certificate, the log, and the outcome it documents, is exactly what ProofWipe recorded at wipe time.

Certificates produced before the wipe-log file shipped print the hash but have no log file beside them; for those, verification requires the retained log from your records.

No lookups, by design

There is no certificate database behind this page. ProofWipe is offline and phone-home-free, so certificates are verified cryptographically from the documents themselves, the same result here, at an auditor’s desk, or on an air-gapped machine.