Skip to content
For people outside the companyForEveryoneWith or without Foxden Admin

Verify a signed document ​

This page is for anyone who holds a document signed through Corsac and wants to check it: that it is the document everyone signed, that nothing changed afterwards, and who signed it when. You need no account.

Open the verify page ​

Every signed document has its own verify link. You find it:

  • in the Completed: email every person on the document received, after "Check this document at any time";
  • on the document's page in Corsac, under Sealed document, for the people who sent it.

Open the link. The page shows the document's name, when signing finished and when it was sealed, then a verdict.

Read the verdict ​

The box at the top gives the verdict:

VerdictWhat it means
Document verifiedEveryone finished signing. The record of events is intact, and the sealed file is exactly what was presented for signature.
Signing is still in progressNot everyone has finished. What has been recorded so far is intact.
This document was declined, voided or expiredIt ended without everyone signing. The reason, if one was given, is shown, and the event list says how it got there.
This document could not be verifiedThe record of events or the sealed file does not check out. Treat the contents as unproven and contact the sender.

Under the verdict, two lines say whether the Evidence chain intact and the Presented state reproducible checks passed.

Download the evidence ​

Under Downloads:

  • Signed document (PDF): the sealed copy.
  • Certificate of completion (PDF): who took part, every event, and the fingerprints of the original and the signed file.
  • Evidence chain (JSON): every event in a form a program can recheck without any access to the sender's systems. It includes each signer's IP address and browser.

Check the details ​

  • Artifact revisions: each version of the sealed file with its SHA-256 fingerprint. Revision 1 is the sealed copy; revision 2 adds the trusted timestamp.
  • Seal identity: Sealed by names the company's seal certificate, and Certificate fingerprint (SHA-256) identifies it.
  • Trusted timestamp: whether an outside timestamp authority stamped the sealed file. Sealed without trusted timestamp means none could be reached: the seal is still valid, but its time comes from the sender's server only.
  • Event timeline: every event, oldest first, in UTC.

Check the seal certificate yourself ​

The sending company publishes the fingerprint of every seal certificate it has used, one per line, at /.well-known/corsac-seal on its Corsac address (the same address the verify link starts with). Compare it with the Certificate fingerprint (SHA-256) on the verify page, and with the fingerprint printed in your completion email. If they match, the document was sealed by that company's server.

What the check does not prove ​

  • The seal is the company's own unless it imported a certificate from a certificate authority. A PDF reader may warn that the signer is unknown, and the EU DSS validator reports INDETERMINATE / NO_CERTIFICATE_CHAIN_FOUND. That means the seal is not a qualified one, not that the file was changed: a changed file fails the check outright.
  • Corsac is not an eIDAS advanced or qualified electronic signature service. The certificate of completion says so.

If the page does not open ​

Too many requests means the link was opened too often from your network. Wait a minute and reload. If the link no longer opens at all, ask the company that sent the document for it again.

Foxden is open source under Apache-2.0.