Check a trusted timestamp
Drop a .tsr or .tst and the file it is for. See when it was stamped, by which authority, and whether the signature and certificate hold up. The file is hashed here and never uploaded.
The timestamp and the file
Drop the timestamp (.tsr or .tst) and the file it is for. A request (.tsq) or the authority's certificate can go in too.
What the timestamp says
The authority's certificates
How it works
What a trusted timestamp is
A trusted timestamp proves a file existed at a certain moment without anyone seeing the file. Its hash is sent to a timestamping authority, which signs a statement of that hash and the time, and sends it back as a .tsr file. The format is RFC 3161. It is how lab notebooks, source code, evidence files, invoices and signed documents are dated so that the date holds up later, and it is what the timestamp on a long-term PDF or e-mail signature is made of.
What is checked
- That it is for this file. The file is hashed in your browser and compared with the hash the timestamp records. A hash pasted instead works the same way.
- That the authority signed it. The signature is checked against the authority's certificate with your browser's own cryptography, and so is the certificate the timestamp names by hash, so one cannot be swapped for another.
- That the certificate is fit for it. RFC 3161 wants a certificate issued for timestamping and nothing else, with that marked critical, and valid at the moment it stamped.
- That it answers the request. With the .tsq that was sent, the hash, the nonce and the policy are matched, which shows the response was issued for that request and not replayed.
- Where the authority's certificate comes from. Each certificate included is checked against the one above it, up to the root, which is named with its fingerprint.
What it does not do
It does not decide whether the authority is one you trust, which depends on the roots your own systems hold. It does not check revocation, which would mean asking the certificate authority over the network. It does not read RFC 5544 timestamped-data files (.tsd), only the .tsr and .tst that RFC 3161 defines. The file is hashed in this tab and only the comparison is shown.
Questions people ask about STAMP
How do I verify a .tsr timestamp file?
Drop the .tsr and the file it is for on this page. STAMP hashes the file in your browser, compares it with the hash in the timestamp, and checks the authority’s signature and certificate. The OpenSSL equivalent is openssl ts -verify -data file -in file.tsr -CAfile root.pem.
What is a .tsr file?
A time-stamp response from a timestamping authority, as defined in RFC 3161. It holds a signed statement that a particular hash existed at a particular time. The .tst is the same token without the response around it.
Does the timestamping authority see my file?
No. Only the file’s hash is sent when a timestamp is made, and when it is checked here the file is hashed in your browser.
What does 'imprint does not match' mean?
The hash of the file you have is not the hash that was timestamped. Either it is a different file, or it has changed, even by one byte, or been saved again since. The timestamp says nothing about it.
Is a timestamp still valid after the authority’s certificate expires?
Yes, if the certificate was valid when the timestamp was made. STAMP checks the certificate against the time in the timestamp, not today’s date.
What is the nonce in a timestamp request?
A random number the requester sends, which the authority copies into its response. Matching it proves the response was made for that request and is not an old one replayed.
Doing this often? PDF Studio signs PDFs with your own certificate and adds a trusted timestamp, so the signature can be checked later. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.