Demo - Step 1

ADSS Signing Server
Server-side complete verification of signed PKCS#7/CMS documents
You can verify any signed PKCS#7/CMS document in this demo. The Ascertia ADSS demo Verification Server has a list of Certificate Authorities (CAs) trusted to issue certificates to end-users as listed here. Only if your document is signed using a credential from one of these CAs it will be shown as trusted. The ADSS Verification Server can support an unlimited number of CAs each with their own validation policy.
1
Select a document
Use a standard contract.pkcs7 document
already held on the server
Use an expired signed contract.pkcs7 document
already held on the server
Use a revoked signed contract.pkcs7 document
already held on the server
Use my own document, which I will upload
(see note below on restrictions on
document size)
 
  Ascertia detailed XML response
OASIS DSS standard XML respons
VERIFY
Server-side verification uses a flexible OASIS DSS API that can define how ADSS Server should verify the signature and what evidence information should be returned, e.g. CRL/OCSP revocation information, certificate path information, etc.

All verification service responses are signed by the ADSS Verification Server so that clients can see that these are genuine messages from a trusted authority and they have not been changed.

The ADSS Verification Server not only ensures that the document has not been changed since signing and that the signer’s credentials are valid (not expired, not revoked and issued by a trusted CA) but can also report on the quality level of the signature and the associated certificate quality level – see this information on PEPPOL.

If you are uploading a document we restrict the file size to  and documents having 50 pages or less – just for this demo.