RFC 3161 Trusted Timestamping
Prove exactly when a document was signed with cryptographic timestamps from independent Time Stamp Authorities. Court-admissible, tamper-proof, and automatically applied.
Timestamping Features
Independent, cryptographic proof of signing time, not just a server clock.
Certified TSA Timestamps
Timestamps issued by accredited Time Stamp Authorities, independent third-party proof of signing time.
RFC 3161 Compliant
Implements the Internet Engineering Task Force (IETF) RFC 3161 standard for trusted timestamping.
Tamper-Proof Time Proof
Timestamps are cryptographically signed by the TSA, impossible to alter the recorded signing time.
Embedded in PDF
The timestamp token is embedded directly in the digitally signed PDF for self-contained verification.
Legal Admissibility
RFC 3161 timestamps are recognized as evidence in courts worldwide, proving the document existed at a specific time.
Long-Term Validity
Timestamps remain valid indefinitely, even after your signing certificate expires.
Multiple TSA Support
Configure any RFC 3161-compliant TSA endpoint, FreeTSA, DigiCert, GlobalSign, Sectigo, and more.
Automatic Application
Timestamps are applied automatically when documents are signed, no manual steps required.
How It Works
Document Hash Generated
When a document is signed, WPsigner generates a SHA-256 hash of the complete signed document.
TSA Request
The document hash is sent to the configured Time Stamp Authority via the RFC 3161 protocol. The TSA creates a timestamp token signed with its own certificate.
Token Embedded
The signed timestamp token is embedded into the PDF's digital signature. Anyone can verify the exact signing time using any compliant PDF reader.
Frequently Asked Questions
What is RFC 3161 timestamping?
RFC 3161 is an internet standard that defines a protocol for trusted timestamping. A Time Stamp Authority (TSA), an independent third party, issues a cryptographically signed token proving that a specific data hash existed at a specific time. This is much stronger than a simple server clock timestamp because it comes from a trusted, independent source.
Why is trusted timestamping important?
Server timestamps can be manipulated by changing the system clock. RFC 3161 timestamps cannot, they come from an independent TSA with its own certificate. This matters in legal disputes where the signing time is contested, in intellectual property claims where priority dates matter, and in regulatory compliance where audit trails require verifiable timestamps.
Does this cost extra?
No. RFC 3161 timestamping is included in every WPsigner plan. WPsigner includes a default TSA configuration. If you prefer a specific TSA provider (DigiCert, GlobalSign, etc.), you can configure any RFC 3161-compliant endpoint in settings.
How is this different from a regular timestamp?
A regular timestamp records the time from your server's clock, which can be changed by anyone with admin access. An RFC 3161 timestamp comes from a trusted third-party TSA with its own cryptographic certificate. It provides independent, court-admissible proof that the signature occurred at a specific time.
Certified Timestamps on Every Document
RFC 3161 timestamping is included in every WPsigner plan. No add-ons required.
View Pricing