Feature
Every document signed through Docuplete receives a trusted timestamp from an independent RFC 3161-compliant time-stamping authority. This provides independently verifiable, tamper-proof proof of exactly when the signature was applied.
How it works
Details
RFC 3161 is the Internet standard for trusted timestamping. A compliant timestamp authority (TSA) signs a hash of your document with its own private key and records the time — creating a cryptographic proof of when the document existed.
Without a trusted timestamp, a signature's legal value can erode if the signing certificate later expires. An RFC 3161 timestamp locks in the validity of the signature at the moment it was applied — for years or decades.
There's no extra step. After a client signs through Docuplete, the trusted timestamp is applied automatically before the completed document is delivered.
The timestamp is cryptographically linked to a hash of the specific document. If any byte of the document changes after signing, the timestamp verification fails — detecting tampering immediately.
Anyone can verify a Docuplete timestamp using standard RFC 3161 verification tools — without needing a Docuplete account or API access.
Docuplete also records a SHA-256 hash of every completed document. Together with the trusted timestamp, this provides two independent layers of tamper detection.
14-day free trial. No credit card. Cancel anytime.
Start free trialStarts at $69/mo.
Related