Verify a sealed CIPC report

A team4u sealed report carries a standard PAdES digital signature and an RFC-3161 timestamp, so you can check it yourself with ordinary tools — you never need to trust us to read the result.
Online checking is temporarily unavailable. The upload-and-check service on this page is switched off while it is being upgraded. Until it returns you can check a report's signature offline with the steps below. An offline check is a standard signature check, not the complete team4u seal check — see what it does and does not prove, below.

What an offline check proves — and what it does not

If every item in step 2 shows as stated, the offline check establishes that the signed content is intact (unchanged since it was sealed), that it was signed with our published report-signing certificate, and that it carries a valid trusted timestamp. It catches an unsigned file, a different signer, a missing or untrusted timestamp, and content changed after sealing.
It does not establish everything the full team4u check does. In particular it cannot detect extra data appended to the file after the sealed part: in our own tests (the standard check as the pyHanko validator, version 0.35.2, performs it), files with bytes added after the seal still pass, while the full team4u check rejects them. It also does not check the report's embedded team4u record. If you need the complete team4u verdict before online checking returns, ask the sender of the report to request a team4u check.

1 · Get our certificates

team4u CIPC Demo CA (team4u-cipc-ca.crt) — the root you trust. Trusting it means trusting every certificate it issues, which is why step 2 also checks the SIGNER's own fingerprint below. SHA-256 fingerprint: 97:7A:32:39:F8:3E:CA:69:35:EF:B1:33:F6:21:F5:F5:1E:9D:6B:99:88:EA:02:47:F2:FF:E6:6F:B9:42:78:0D
team4u report signer (team4u-cipc-signer.crt) — the certificate the seal is made with (valid to 22 July 2031). SHA-256 fingerprint:
6D:56:50:2E:59:30:5E:E2:F2:FE:ED:17:8D:7F:7C:64:00:34:6D:1E:5F:48:FE:29:DB:97:D9:91:57:B3:A6:34
Before you trust a downloaded certificate, check that its SHA-256 fingerprint matches the one printed here, e.g. openssl x509 -in team4u-cipc-ca.crt -noout -fingerprint -sha256.

2 · Check the report — Adobe Acrobat Reader (free)

We have not yet tested these Adobe steps on a recipient's computer. Adobe's menus and the wording of its results differ between versions. What we have tested is the same standard check with the pyHanko validator (0.35.2) on our own test files. If Adobe does not clearly show one of the items below, treat the check as inconclusive.
  1. Edit → Preferences → Signatures → Identities & Trusted Certificates → More… → Trusted Certificates → Import.
  2. Choose team4u-cipc-ca.crt, select it in the list, Trust… → tick Use this certificate as a trusted root → OK.
  3. Open the report → Signature Panel → Validate All, then open the signature's details.
The report passes the offline check only if ALL of these show:
  1. the Signature Panel lists exactly one signature, team4u Certified CIPC Report (DEMO SEAL). An entry shown as a document timestamp is an archival timestamp, not a signature, and may follow it. Any second signature — by anyone, team4u included — means the file was changed after sealing;
  2. that signature is valid;
  3. the document has not been modified since this signature was applied;
  4. the signer is team4u Certified CIPC Report (DEMO SEAL) and, in its certificate details (Show Signer's Certificate → Details), the SHA-256 digest equals the signer fingerprint above;
  5. the signature is timestamped and the timestamp itself is shown as valid / verified (the timestamp authority is DigiCert, which Adobe already trusts).
If any item shows something else — invalid, modified, a different signer or fingerprint, more than one signature — do not rely on the document. If an item cannot be confirmed (for example the timestamp shows as "not verified" or "unknown"), the check is inconclusive: not a pass.

← back to lookup · The complete team4u check (online, when it returns) confirms that team4u signed the report, that the whole file is exactly what was sealed — nothing changed or appended afterwards other than permitted archival timestamps — and that it carries a trusted RFC-3161 timestamp; the offline check covers the parts listed above. The current seals are demo seals, labelled "not for legal reliance"; production seals will use a document-signing certificate.