You have a file and a timestamp that says the file existed on 3 March. The other side's lawyer asks one question: is that a qualified timestamp? If you cannot answer, or the answer is no, you need to know what you have lost, and whether it matters.
In the EU, the answer comes from two articles of the eIDAS Regulation, Regulation (EU) No 910/2014. They are short. This post sets out what they say, what "qualified" adds, how to check whether a given timestamp is qualified, and when an ordinary one is enough.
Two kinds of timestamp, one difference in law
eIDAS defines an electronic timestamp as "data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time" (Article 3(33)). A qualified electronic timestamp is one "which meets the requirements laid down in Article 42" (Article 3(34)).
Article 41 then gives each kind its legal effect:
- Any electronic timestamp "shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements of the qualified electronic time stamp".
- A qualified one "shall enjoy the presumption of the accuracy of the date and the time it indicates and the integrity of the data to which the date and time are bound".
- A qualified timestamp issued in one member state "shall be recognised as a qualified electronic time stamp in all Member States".
So the difference is not admissibility. A court in the EU cannot refuse a timestamp only because it is not qualified. The difference is who has to do the work. With a qualified timestamp, the date and the integrity of the file are presumed, and the party who disputes them has to displace that. With any other timestamp, you have to show why it deserves to be believed.
| Qualified timestamp | Any other timestamp | |
|---|---|---|
| Can be refused as evidence for being electronic or not qualified | No | No |
| Date and time presumed accurate | Yes | No, you prove it |
| Integrity of the stamped data presumed | Yes | No, you prove it |
| Recognised as qualified in every member state | Yes | Not applicable |
| Who can issue it | A qualified trust service provider on a national trusted list | Anyone |
What makes a timestamp qualified
Article 42 sets three requirements. A qualified timestamp:
- "binds the date and time to data in such a manner as to reasonably preclude the possibility of the data being changed undetectably";
- "is based on an accurate time source linked to Coordinated Universal Time"; and
- "is signed using an advanced electronic signature or sealed with an advanced electronic seal of the qualified trust service provider, or by some equivalent method".
The first two describe what any timestamping authority should do. The third is the one that decides the matter: the signer must be a qualified trust service provider. That is a status, not a description. Article 3(20) defines such a provider as one that "is granted the qualified status by the supervisory body".
Getting the status takes three steps under the regulation:
- The provider notifies its national supervisory body and submits a conformity assessment report from a conformity assessment body (Article 21(1)).
- The supervisory body verifies compliance and, if satisfied, grants qualified status. The provider may begin the qualified service only "after the qualified status has been indicated in the trusted lists" (Article 21(3)).
- After that, the provider is "audited at their own expense at least every 24 months by a conformity assessment body" (Article 20(1)).
The presumption in Article 41 is the law's side of that bargain. A regulator has already examined the provider, so the court does not start from nothing.
The file format tells you nothing
A common mistake is to treat "RFC 3161" and "qualified" as two grades of the same thing. They are answers to different questions. RFC 3161 is a technical standard for the token: what goes in it and how it is signed. Qualified is a legal status of the service that issued it.
eIDAS names no file format. Article 42 even allows "some equivalent method" to a signature or seal, and recital 62 says it is for the provider to show in its conformity assessment report that such a method is as secure. So a token in the standard format, from a well-known authority, that verifies perfectly, can still be non-qualified. A timestamp is qualified because of who issued it and under what supervision, and for no other reason.
How to check whether a timestamp is qualified
Do not take a vendor's word for it, in either direction. The check takes a few minutes.
- Find out who signed the token and under which policy. The authority is named in the token's signing certificate, and the token states its policy. Our guide to verifying an RFC 3161 timestamp with OpenSSL shows how to read a token.
- Look the provider up on a trusted list. Each member state must "establish, maintain and publish trusted lists" of the qualified providers it is responsible for and their qualified services (Article 22(1)). The Commission's page on EU trusted lists links to a browser for all of them.
- Check the service, not only the company. The entry you need is the provider's timestamping service, marked as qualified. The Commission notes that member states may also list non-qualified services, marked as such, so a provider's name on a list is not enough.
- Check the status on the date of the timestamp. What matters is whether the service was qualified when the token was signed, not whether it is today.
The list is decisive. In the Commission's words, national trusted lists "have a constitutive effect": a provider and its service "will be qualified only if it appears in a trusted list". A logo, a certificate of conformity or the word "eIDAS" on a pricing page does not make a timestamp qualified.
What the presumption does not cover
The presumption has two parts: the time is accurate, and the data bound to it has not changed. It says nothing else.
- It does not prove the content is true or genuine. A qualified timestamp on a capture of a web page shows the capture existed at that time. Whether it is a faithful copy of the page is a separate question, answered by how the capture was made and who has held it since.
- It does not show when the file was created. Only that it existed by the stated time.
- It is a presumption, not a finding. The regulation does not say how it may be challenged. Recital 22 leaves that to member states: "It is for the national law to define the legal effect of trust services, except if otherwise provided in this Regulation."
The position in the UK
The UK kept the regulation after leaving the EU, with changes. The UK version of Article 41 keeps the first two rules word for word: no denial of legal effect, and a presumption for qualified timestamps. The third paragraph, on recognition across member states, was omitted with effect from 31 December 2020.
In practice the presumption is hard to use in the UK. The Information Commissioner's Office (ICO) supervises trust services and publishes the UK trusted list. Its page of approved providers said this when we checked on 13 November 2026: "There are currently no UK trust service providers with qualified status." Do not assume that a timestamp qualified in an EU member state counts as qualified under the UK version. Ask the lawyer who will rely on it.
Do you need one?
You need a qualified timestamp when:
- A rule, a regulator, a tender or a contract asks for one by name. Nothing else meets a requirement written that way.
- The date is the point most likely to be attacked, in proceedings in an EU member state. If the case turns on what existed on a given day, and you expect the other side to contest it, the presumption moves the work to them.
An ordinary timestamp from an independent authority is usually enough when:
- The date is corroborated in other ways. Emails, server logs, a witness and a capture record that all agree leave little to dispute.
- The forum is outside the EU. Article 41 is EU law. Elsewhere the timestamp is weighed as evidence on its merits, whatever its status. Our post on web pages as evidence in England and Wales covers one such forum.
- You can prove it yourself. A non-qualified token that anyone can verify against the file, from an authority with nothing to gain, is still evidence that the file existed then. You will have to explain it; you will not be presumed right.
You can also add one later. A timestamp covers a file's hash, so a file you already hold can be sent to a qualified provider at any time. The new stamp proves the file existed on the day you asked, not on the day it was made, so do it early if you think you will need it.
Where Archivepanel fits
Archivepanel's timestamps are not qualified. When a capture of a public page completes, DigiCert signs an RFC 3161 timestamp over the SHA-256 digest of the saved HTML file. In EU proceedings that puts it under the first rule of Article 41: it cannot be refused for not being qualified, and it carries no presumption.
What it gives you is a date that does not depend on our word or yours, and the means to prove it. The token downloads with the file, anyone can check the pair with OpenSSL without an account, and we renew tokens before their certificates expire so they stay checkable. The timestamps page explains how.
If your matter needs a qualified timestamp, download the capture and have that same file stamped by a qualified provider from a trusted list. Keep both tokens: ours shows the earlier time, theirs carries the presumption from the later one. The free tier holds 100 MB.
Sources
- Regulation (EU) No 910/2014 (eIDAS), EUR-Lex. The text as adopted is also published on legislation.gov.uk, which is where we checked each quotation: Article 3, points 20, 33 and 34; Article 20; Article 21; Article 22; Article 41; Article 42; and recitals 22 and 62.
- Article 41 as it applies in the UK, legislation.gov.uk, with the omission of paragraph 3.
- European Commission, EU trusted lists, on the constitutive effect of the lists and the trusted list browser.
- Information Commissioner's Office, UK trusted list and approved qualified trust service providers, checked 13 November 2026.
- RFC 3161, Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP), August 2001.