How it works

Three steps, in everyday words: how a document is signed, how Onwyn seals it, and what each way of checking it actually checks.

1. Signing

The sender uploads a document and names who should sign it. Each signer gets a personal link by email. Usually they must also type a one-time code that we email to them, which shows they controlled that email address at that moment; the sender can choose to skip the code, and the evidence record says which was used. The signer reads the document, agrees, and signs. Every step is recorded with its time.

This is not an ID check: nobody looks at a passport or an ID card. Documents sealed on seal.onwyn involve no signer at all.

2. Sealing

When the document is complete, Onwyn applies a digital seal. The seal is a cryptographic fingerprint of the whole file, locked with Onwyn's certificate, plus a timestamp. If a single byte of the file changes afterwards, the fingerprint no longer matches and any check of the seal shows it.

The time comes from Onwyn's own timestamp service.

3. Verifying

With the code printed on the document

Typing the code printed on the document looks it up in Onwyn's records. It tells you whether Onwyn sealed a document under that code, for which company and on which day, and whether the copy Onwyn holds still matches its seal. It does not look at the copy in your hand.

With the PDF itself

Uploading the PDF checks the file itself: its seal, the certificates the seal chains to, the timestamp, and whether the bytes are exactly the bytes that were sealed. Only an upload compares the actual bytes of your copy. The file is processed in memory and discarded.

Check a document Enter a code

What this proves

  • That the file you uploaded is, byte for byte, the file Onwyn sealed.
  • That Onwyn sealed it, for the company named in the seal, at the time in the seal.
  • How each signer was let in (an emailed code, or the link alone) and what they did, with times. This is in the evidence record, not in the PDF.

What this does not prove

  • The legal identity of a signer. Nobody's ID document was checked; a signer is known by the email address they controlled.
  • That the time came from an independent clock: the timestamp currently comes from Onwyn's own time service.
  • That this is the highest level of electronic signature under the EU eIDAS Regulation. That level needs a certificate from a government-supervised trust service provider, and Onwyn is not one.
  • That the content is true or complete. Onwyn seals the file as it was given; it does not read it.
  • This check does not tell you whether the document needed a stronger form of signature under the law that applies to it.

The technical detail — certificates, revocation lists, the sealing policy and the validator we use — is on the trust page.

How it works, in plain words · Onwyn's certificates, revocation lists 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.