Skip to content

-P5Verify authenticity

Received a PDF or image from us?

Documents and images that leave our house are digitally signed and timestamped. In a few minutes you can check that they really come from us and have not been altered since.

-P5.1

Verify a PDF

Open the PDF in Adobe Acrobat or Acrobat Reader and click “Signature Panel”. As the signer you will see:

  • “H&M Software-Netzwerktechnik-GmbH” — issued by us
  • for approvals, additionally a person from our company — personally approved
  • and a timestamp proving when it was signed
“Valid”Sender confirmed, document unaltered.What to doNothing.
“Validity unknown” and “Document has not been modified”The signature is fine. Your program just does not know our root certificate yet.What to doImport the root certificate once (below).
“Invalid” or “Document has been modified”The document was changed after signing.What to doDo not use it — get in touch.

How to import the root certificate →

A report from MLC Sensor Monitoring?

Temperature and audit reports are signed by the business that runs the system — so the signer shown is their company name, not ours. We are the issuer of the certificate. Verification works exactly as above.

-P5.2

Verify an image

Product images, screenshots and graphics from us carry a C2PA seal (“Content Credentials”) and an ID in the MLC Photo Registry. Any later change to the image breaks the seal.

MLC Photo-Protect app

Checks seal and ID — no account needed. The app looks the ID up in the Photo Registry; only the ID goes over the network, never the image. For Windows, macOS and Linux.

Download ↗

Without an account

Any Content Credentials verification tool shows the seal and whether the image was altered, e.g. contentcredentials.org/verify. It does not know our name as the issuer (yet).

contentcredentials.org ↗

Note: many platforms (social networks, messengers) strip seals on upload. An image without a seal is therefore not automatically fake — if in doubt, ask us.

-P5.3

Our root certificate

Compare the fingerprint before importing. It is shown identically on mlcgo.eu/pki/ — two independent places.

SHA-256
79:3B:0A:48:3A:9B:26:1D:91:BE:C0:33:C9:47:EB:A4:75:38:DA:48:3D:D4:A8:39:52:EF:3C:5D:F5:C9:0C:AB
SHA-1 (Windows)
AA:97:4E:34:1D:F3:38:6A:07:AF:D0:DD:C1:8E:C3:84:9D:AE:13:49

Name in the certificate: “H&M Software-Netzwerktechnik-GmbH Root CA” · valid until 2051

If in doubt: ask us

We keep a log of everything we sign. Send us the document or image — we will tell you whether it came from us exactly like that.

Ask about authenticity →
deen