Skip to main content

Sign and verify locally

· 3 min read
Jan Wittkamp
CEO @ Memida GmbH

Whether a PDF or a digital calibration certificate in DCC format, Memida Signing applies a company seal to your files directly on your computer. The free desktop app also processes documents from other systems. It saves sealed copies and leaves the originals unchanged.

Local sealing requires a valid, supported company certificate, but no Memida account. The app also helps recipients: existing seals can be verified without a certificate of your own. The documents are not uploaded in the process.

Fig. 1: Save multiple files locally as sealed copies

Sealed copies, unchanged originals​

Memida Signing processes multiple selected files together. In this example, Seal 3 files (1) approves the selected batch. Beforehand, the app shows the documents, any exclusions, and the company certificate to be used for review. Final confirmation takes place in the operating system's security dialog.

The Results (2) show whether a sealed copy was saved for each file. Originals and existing destination files are not overwritten. Copies already saved are retained even if the process is canceled. This makes it clear which documents are ready to share and where an error still needs to be resolved.

Supported files

Unsealed DCCs of version 3.3.0 and suitable PDFs that have not yet been signed are supported. The handbook describes the format requirements. The contents still need a technical review before approval.

Verify what the seal establishes​

A valid signature does not answer every question of trust. Under Verify seal, the app therefore distinguishes the cryptographic signature, certificate trust, and current revocation status.

Fig. 2: Signature, certificate, and revocation status in the verification result

In the example, the Signature is cryptographically valid (1), the Certificate is not trusted (2), and the current revocation status has not been checked (3). The signed data is unchanged; this alone does not establish trust in the certificate. A seal verification record can be saved as HTML or JSON to retain the results.

Work locally and add a revocation check​

Local sealing and verification work without an internet connection. The optional online check adds the current revocation status using public certificate revocation lists from D-Trust. It downloads these lists without transmitting documents, certificates, or passwords. If enabled during sealing, a sealed copy is created only when the current revocation status is confirmed. Without this option, the current revocation status remains undetermined.

Seal verification does not confirm correct calibration results, DCC schema compliance, accreditation scope, or historical validity. Local sealing does not add a trusted timestamp. The seal verification record therefore does not replace a technical inspection report.


Memida Signing is available on the downloads page. The handbook describes setup, supported formats, and the meaning of verification results.