Find and download a certificate
The certificate list, the certificate page, the PDF and the canonical JSON.
Every proof that passes the checks becomes a certificate. Every role can view and download certificates.
Find a certificate
Click Certificates in the sidebar. The page counts your certificates (total, certified, revoked) and lists them with their identifier, issue date, organization, status and whether they are anchored on the blockchain.
Use the search field to find a certificate by any of these values, and the Status filter to show only the certified or revoked ones. From a proof, the View certificate link opens its certificate directly.
The certificate page
Click View to open a certificate. Its page has three parts.
Actions. Download PDF, Download canonical.json and, for client admins, Revoke.
Metadata.
| Field | What it is |
|---|---|
| Issued at | Date and time the certificate was issued. |
| Canonical hash | The fingerprint of the canonical JSON. It identifies the certificate and is what the blockchain records. |
| HMAC key ID | The key the portal used to seal the certificate, so it can detect any later change. |
| PAdES signature | The electronic signature of the PDF and the certificate that signed it. |
| Blockchain | Anchored, with the chain and a View on explorer link to the public transaction; or Not anchored on an instance without blockchain. |
| Public verification code | The code printed on the PDF, to verify the certificate on the public page. |
State history. When the certificate was issued and, if it happened, when it was revoked.
The PDF
The PDF is the document you hand out. It is signed electronically and contains:
- the wipe result, in large type: all disks cleaned, partial wipe, or not confirmed;
- the machine erased, with its UUID on a line of its own, the wipe profile (method used and number of overwrite passes, or per disk when the disks ran different counts), the operator and the timeline of the session;
- the disk erasure evidence: one line per disk with its status, model, size and the verification of its erasure (method, scope, result, and why the blocks read could not be compared when they could not), plus its number of passes when the disks ran different counts. Three overwrite passes are the DoD 5220.22-M method;
- the blockchain anchor, when there is one;
- the verification code and a QR code that opens the public verification page.
On a partial wipe, only the disks marked CLEANED are certified, and only they used a license.
Open the PDF in a reader that shows signatures (Adobe Acrobat Reader, for example) to see that the signature is valid and that the document has not been modified since.
The canonical JSON
canonical.json holds the same content as the PDF in a structured form, including the proof
produced by the agent. It is meant for your tools: archiving, asset management, or checking the
certificate independently by recomputing its fingerprint.
Hand out a certificate
Send the PDF to whoever needs it. They do not need a Wipe account: the QR code or the verification code is enough to check it. See Verify a certificate.