Trust: Onwyn certificates and sealing policy
sign.onwyn, seal.onwyn and verify.onwyn are one product: a document is signed or sealed, and anyone can verify the result.
This page publishes what you need to check a document sealed by Onwyn without asking Onwyn: the certificates the seal chains to, the revocation lists, and the rules the seal follows.
Certificates
| Certificate | Subject | Valid from | Valid until | Download |
|---|---|---|---|---|
| Root | Onwyn Sign Root CA CN=Onwyn Sign Root CA,O=Onwyn Sign,C=DE |
root.cer | ||
| Issuing | Onwyn Sign Issuing CA CN=Onwyn Sign Issuing CA,O=Onwyn Sign,C=DE |
issuing.cer | ||
| Timestamp | Onwyn Sign Timestamp CN=Onwyn Sign Timestamp,O=Onwyn Sign,C=DE |
tsa.cer | ||
| Seal | Onwyn Sign CN=Onwyn Sign,O=Onwyn Sign,C=DE |
embedded in every sealed PDF |
SHA-256 fingerprint of the root certificate: 8F:36:12:5E:C0:3F:2C:B2:74:7A:7B:C4:42:35:B0:82:53:E0:DA:B4:C2:EA:22:AC:41:E1:45:1B:A1:E6:0B:D3
Root certificate as PEM (root.pem)
-----BEGIN CERTIFICATE----- MIIB/TCCAYSgAwIBAgIQH9eXhbrSnj94RbW8WOAEkDAKBggqhkjOPQQDAjA/MQsw CQYDVQQGEwJERTETMBEGA1UECgwKT253eW4gU2lnbjEbMBkGA1UEAwwST253eW4g U2lnbiBSb290IENBMB4XDTI2MDkxOTA4MjcyOVoXDTQ2MDkxNDA4MzIyOVowPzEL MAkGA1UEBhMCREUxEzARBgNVBAoMCk9ud3luIFNpZ24xGzAZBgNVBAMMEk9ud3lu IFNpZ24gUm9vdCBDQTB2MBAGByqGSM49AgEGBSuBBAAiA2IABA8BSwIGTv4kVaM8 Hydn+5fqHL90QE1254Q1oyYJpYWv5717YHGpsSPELRjJNV1gS5gY8l4AD8lSfwZ9 LL9zVYuvr9oo9s35ggb3tg8oxfnvXg0hUtUnF+aTbzYzGdkAmKNFMEMwHQYDVR0O BBYEFA5V9Cm0YEhJXjQNSjwRq05aXvKwMBIGA1UdEwEB/wQIMAYBAf8CAQEwDgYD VR0PAQH/BAQDAgEGMAoGCCqGSM49BAMCA2cAMGQCME+O5Bdv0IAXzYL0nwSC9x6r 1bMqFcawEEMuzoOobMJ61ro3gBWJh9ERBEGJwRn6owIwYJ4cXIQifuY10YG1T5Pl edeIchGE+loG720s9aoB48IhOW5GbtntMvxomFVlvTQ7 -----END CERTIFICATE-----
Revocation lists
| List | Issued by | Issued | Next update | Revoked | Download |
|---|---|---|---|---|---|
| issuing.crl | Onwyn Sign Issuing CA | 0 | issuing.crl | ||
| root.crl | Onwyn Sign Root CA | 0 | root.crl |
Sealing policy
What a seal proves
- The seal proves the document has not changed since the time shown in the seal.
- The seal was applied by Onwyn, for the customer named in the seal block, on the document whose SHA-256 the seal records.
- The time comes from Onwyn's own timestamp service.
What a seal does not prove
- The identity of any person. A seal applied on seal.onwyn involves no signer; on sign.onwyn the signer's identity assurance is stated separately in the evidence package.
- This check does not tell you whether the document needed a stronger form of signature under the law that applies to it.
- That the content is true or complete. Onwyn seals the file as uploaded; it does not read it.
How the seal is made
- PAdES B-LT signature with the 'Onwyn Sign' certificate, issued by 'Onwyn Sign Issuing CA' under 'Onwyn Sign Root CA' (ECDSA P-384, SHA-256). Revocation data is embedded, so the PDF can be checked offline.
- Timestamp policy OID 1.3.6.1.4.1.99999.1.1 (Onwyn's private arc). Every timestamp token is RFC 3161 and names this policy.
- Every seal job writes an evidence chain (sha256-linked events) that the evidence package carries as events.jsonl, with a timestamp token over the manifest.
- The verify page checks seals with pyHanko, an open-source PDF signature validator, against the root certificate published on this page. Any other PAdES validator given the same root can repeat the check.
How to check a sealed document
The quickest check is https://verify.onwyn.io: drop the PDF there, or type the code printed on it. No account is needed and the file is discarded after the check.
To check without asking Onwyn anything, download root.cer above (or copy root.pem) and give it to any PDF signature validator as the trust anchor. Every Onwyn seal is a standard PAdES B-LT signature with its revocation data embedded, and every timestamp token is standard RFC 3161, so a validator needs nothing from us but this certificate.
Each evidence package carries the same certificates in its trust/ folder, together with the document, the original, the recorded events and a timestamp token over the manifest. The package README says, in the document's language, what each member is and how the hashes fit together.