Skip to content
සියලු මෙවලම්

ඩිජිටල් අත්සන

Premium+

PKCS#7 ක්‍රිප්ටොග්‍රැෆික් අත්සන

1උඩුගත කරන්න
2වින්‍යාස කරන්න
3සකසන්න

Drop file here

PDF, Word, Excel, PowerPoint, images up to 25 MB

ප්‍රධාන විශේෂාංග

  • PKCS#7/CMS (PAdES) certificate-based signatures
  • Supports Advanced and Qualified Electronic Signatures
  • Upload PKCS#12 (.p12/.pfx) personal certificates
  • RFC 3161 trusted timestamp by default
  • Signature verification embedded in PDF output
  • Tamper-evident — any modification invalidates signature
  • Multi-signatory workflows with sequential signing order
  • Visual signature representation on the page
  • Long-term validation (LTV) data embedded
  • Works with certificates from any qualified trust service provider
  • Signature reason and location metadata
  • Certificate chain validation before signing
  • Batch signing for multiple documents
  • Private keys processed in memory only — never stored

භාවිත අවස්ථා

  • Signing cross-border commercial contracts under eIDAS
  • Government tender and procurement submissions
  • Regulated financial institution document signing
  • Healthcare provider consent and clinical trial authorisations
  • Legal notarisation of digital documents
  • Accounting firm client report sign-off
  • Real estate transaction document signing
  • Insurance policy issuance and claims
  • Pharmaceutical regulatory submission signing
  • High-value purchase agreements requiring qualified signatures

භාවිත කරන ආකාරය

  1. 1Upload the PDF document you need to sign.
  2. 2Upload your PKCS#12 certificate file (.p12 or .pfx) and enter the certificate password. The private key is used in memory for signing and is never stored.
  3. 3Configure signature metadata: signing reason, location, and whether to apply a visible signature appearance on the page.
  4. 4Click Sign Document. The tool creates a cryptographic hash of the PDF, signs it with your certificate, and embeds the signature with a trusted timestamp.
  5. 5Download the signed PDF. Open it in Acrobat Reader to verify the signature panel shows a green checkmark confirming the signature is valid and the document has not been modified.

For most everyday documents, an electronic signature is sufficient. But for regulated industries, cross-border legal agreements, government filings, and any document where you need to prove that specific person signed a specific version of a specific document at a specific moment in time, a certificate-based digital signature is what the law and the standard require. Dokk.ai's Digital Sign tool implements PKI-based PDF signatures using PKCS#7/CMS (PAdES format), the standard mandated by EU eIDAS for Advanced and Qualified Electronic Signatures. When you sign a document, the tool creates a cryptographic hash of the PDF content, encrypts it with your private key, and embeds the signature along with your public certificate in the PDF. Any PDF reader can verify this signature independently by decrypting the hash with your public key and confirming it matches the current document state. This architecture makes the signature verifiable by anyone, offline, without trusting Dokk.ai or any intermediary. A modified document fails verification immediately — even a single changed character invalidates the signature. This tamper-evidence is what distinguishes digital signatures from scanned signatures or drawn e-signatures. Dokk.ai supports multiple signing scenarios. Upload your own PKCS#12 (.p12 or .pfx) certificate from a qualified trust service provider. For organisations without individual certificates, the platform supports signing with organisation-level certificates. A trusted timestamp from an RFC 3161 timestamp authority is applied by default, cryptographically proving the signing time. After signing, use the Flatten tool to merge visual signature representation into the page, or Encrypt PDF to add a password layer. Fill & Sign handles the earlier document completion step if the document is also a form. Certificate management settings let you store and manage your certificates for reuse across multiple signing sessions. All private keys are processed in memory only and never written to disk or stored in any form.

නිතර අසන ප්‍රශ්න

ආරක්ෂාව සහ පෞද්ගලිකත්වය

Private keys from uploaded certificates are processed in memory only and never written to disk or logged. Certificate files are deleted immediately after signing. The signed PDF is available for download for 1 hour before deletion. TLS encryption in transit. Dokk.ai does not retain certificates or signing credentials.