RFC 3161 Timestamps: The Legal Standard for Digital Evidence
RFC 3161 Timestamps: The Legal Standard for Digital Evidence
If you've ever needed to prove that a document existed at a specific point in time, you've probably encountered the question of what counts as proof. Not all timestamps are equal — a timestamp you create yourself proves nothing, because you could have backdated it. RFC 3161 solves this problem.
What Is RFC 3161?
RFC 3161 is a technical standard published by the Internet Engineering Task Force (IETF) in 2001. It defines the protocol for requesting and issuing trusted timestamps from independent Time Stamp Authorities (TSAs).
When you submit a document hash to an RFC 3161 TSA:
- The TSA signs the hash with its private key.
- The signature includes the TSA's own highly accurate clock reading.
- The TSA returns a cryptographic receipt — a Time Stamp Token (TST).
The TST proves that the TSA saw your hash at that exact moment. Because the TSA is independent and uses a trusted clock, the timestamp cannot be forged or backdated.
Why Courts and Regulators Accept It
RFC 3161 timestamps are recognised as legally admissible evidence under several major legal frameworks:
- eIDAS (EU): The European Union's electronic identification regulation explicitly recognises qualified electronic timestamps based on RFC 3161 as having legal effect equivalent to handwritten signatures in many contexts.
- ESIGN Act and UETA (USA): While US law focuses on electronic signatures rather than timestamps specifically, RFC 3161 timestamps are widely accepted as corroborating evidence in US courts when establishing the existence of a document at a given time.
- Berne Convention: For intellectual property purposes, timestamping a work's hash provides evidence of existence that is recognised in all 180+ Berne Convention signatory countries.
The key property is independence. A timestamp you issue yourself has no legal weight. A timestamp issued by a recognised TSA — and cryptographically signed — carries the same evidentiary weight as a notarised document in many jurisdictions.
How TSA Verification Works
Anyone with your document and its TST can verify the timestamp without contacting the TSA:
- Recompute the SHA-256 hash of the document.
- Check that the hash matches the one inside the TST.
- Verify the TSA's cryptographic signature against the TSA's public certificate.
This verification is entirely offline and needs no special software beyond standard cryptographic tools. The proof is self-contained.
Dual-TSA Timestamping
Provelio submits every hash to two independent TSAs: freetsa.org and the DFN-Verein TSA (operated by the German research network). If one TSA is unavailable, the other provides backup. Having two independent timestamps from different organisations strengthens the evidentiary record — neither TSA has any reason to collude, and an adversary would need to compromise both simultaneously to challenge the timestamp.
RFC 3161 vs. Blockchain Timestamps
RFC 3161 and blockchain timestamps serve complementary roles:
| Property | RFC 3161 | Blockchain OTS |
|---|---|---|
| Speed | Immediate (seconds) | ~minutes |
| Legal recognition | Explicit in eIDAS, UETA | Emerging |
| Trust model | Centralised TSA | Decentralised network |
| Immutability | TSA certificate chain | Blockchain |
Provelio issues both. RFC 3161 gives you instant, legally recognised proof. Blockchain anchoring adds a layer of immutability that no TSA can revoke.
Practical Implications
For creators, RFC 3161 timestamps answer the question a judge or licensing board will ask: "How do I know this wasn't backdated?" The answer is straightforward — an independent, auditable third party signed it with their private key at that moment. Forging the timestamp would require breaking RSA cryptography or compromising the TSA's infrastructure, which is not a realistic attack.
For institutions issuing certificates, RFC 3161 provides a tamper-evident seal. If the certificate is altered after issuance, the hash will not match the TST. Verification is instant, global, and requires no contact with the issuing body.
RFC 3161 is not new technology. It has been in production use by banks, governments, and legal systems for over two decades. Provelio makes it accessible to anyone with a file to protect.