The short answer
Under the EU eIDAS Regulation every electronic timestamp can be used as evidence, but only a qualified one comes with a legal presumption. A non-qualified timestamp is admissible and the court weighs it freely. A qualified electronic timestamp is presumed accurate as to its date and time and as to the integrity of the data it is bound to, and it is recognised as qualified in every EU member state. In practice that moves the argument: with a qualified stamp, the other side has to explain why the time or the data should not be trusted; without one, you have to explain why they should.
This guide explains the difference for lawyers, compliance teams and investigators, lists the timestamps that look official but are not qualified, and shows how to check which kind you are holding. It complements our separate articles on Article 41 and Article 42, which go deeper into each provision.
What Article 41 actually says
Article 41 of Regulation (EU) No 910/2014 has three paragraphs, and each does a different job:
- Article 41(1), non-discrimination: an electronic timestamp shall not be denied legal effect and admissibility as evidence solely because it is electronic or because it does not meet the requirements of a qualified timestamp.
- Article 41(2), presumption: a qualified electronic timestamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data to which the date and time are bound.
- Article 41(3), recognition: a qualified electronic timestamp issued in one member state is recognised as a qualified electronic timestamp in all member states.
The 2024 amendment of eIDAS (Regulation (EU) 2024/1183, often called eIDAS 2) kept this structure. On the timestamp side it added a presumption that the Article 42 requirements are met when a provider follows the standards set in implementing acts, today Implementing Regulation (EU) 2025/1929.
What makes a timestamp qualified
Qualified is a legal status, not a quality label a vendor can give itself. A timestamp is qualified only when all of the following hold:
- It meets Article 42(1): date and time are bound to the data so that undetected changes are reasonably precluded, the time comes from an accurate source linked to UTC, and the stamp is signed or sealed by the provider with an advanced electronic signature or seal, or an equivalent method.
- It is issued by a qualified trust service provider under its qualified time-stamping service, after a conformity assessment and a decision of the national supervisory body.
- That service is listed in the national trusted list of the provider's member state with qualified (granted) status at the moment the stamp was issued.
- Since October 2025, providers that follow Implementing Regulation (EU) 2025/1929, which references ETSI EN 319 421 and EN 319 422 with adaptations, benefit from a presumption of compliance with Article 42.
The consequence is easy to miss: qualified and non-qualified time-stamping authorities use the same RFC 3161 token format. You cannot tell them apart from a file name or a report heading, only by checking who signed the token and whether that service was qualified on that date.
Timestamps you already have that are not qualified
Most dates attached to digital evidence are not qualified timestamps, even when they look precise:
- The time visible on a screenshot, the computer clock, or a file's created and modified dates.
- Photo EXIF data and document metadata written by the device or the editing software.
- The Date header of an e-mail and the posting time displayed by a social network.
- Server logs, database records and the time a software tool says it captured a page.
- RFC 3161 tokens from free or commercial time-stamping authorities that are not listed as qualified.
- Blockchain anchors such as OpenTimestamps: useful as an additional, independent layer, but not a qualified timestamp under eIDAS.
None of these is worthless. Under Article 41(1) they remain admissible and a court may well accept them. But their reliability has to be argued: who controlled the clock, whether the data could have been edited, whether the logs are complete. That is usually where expert reports, witness statements and costs come in.
What changes in a dispute
The practical difference appears the moment the other side challenges your evidence:
- Burden of argument: with a qualified stamp, the accuracy of the time and the integrity of the stamped data are presumed until the opponent rebuts the presumption; with a non-qualified one, you have to persuade the court under national rules of evidence.
- Cross-border cases: a stamp that is qualified in one member state is qualified throughout the EU, so a Czech, French or Dutch court does not have to examine a foreign provider from scratch.
- Cost and speed: checking a qualified stamp is quick (validate the token, confirm the provider's status), whereas a non-qualified timeline may need an expert to reconstruct how the times were produced.
- Vague objections: a presumption does not make evidence unchallengeable, but it raises the bar for objections such as 'the file could have been edited later'.
The presumption is rebuttable. An opponent can still argue that the stamped data is not what you say it is, or that it was collected improperly. The stamp narrows the dispute; it does not end it.
What a qualified timestamp does not prove
Overstating the presumption is the quickest way to lose credibility with a judge. A qualified timestamp says nothing about:
- Whether the content is true: a defamatory post stamped at 10:02 is still only proof that this post existed in that form at 10:02.
- Who made the capture, or that it shows what every visitor saw: personalisation, location and logged-in views differ.
- Whether the capture method was sound: an incomplete capture can be stamped as easily as a careful one.
- Anything before the stamp: it proves that the data existed no later than the stated time.
That is why the capture method matters as much as the stamp: a documented process (who, which tool, which artifacts, which interventions), raw artifacts such as HTML and network logs, and a clear chain of custody. ISO/IEC 27037 and the Council of Europe guidelines on electronic evidence are useful references for that part.
How to check whether a timestamp is really qualified
Whether you receive evidence from the other side or prepare your own, run the same five checks:
- Extract the timestamp token (in a ZIP package usually a .tsr file, in a PDF the document timestamp) and confirm that it validates against the data it claims to cover.
- Identify the time-stamping authority from the certificate that signed the token.
- Look up that provider in the EU trusted lists, which the European Commission makes searchable, and find its time-stamping service with the qualified service type.
- Check that the service had granted status on the date shown in the stamp, not only today.
- Confirm that the hashes in the stamped data match the files you rely on: a valid stamp over different data proves nothing about yours.
Good tooling does this for you and does not ask you to trust the vendor. A package that carries the relevant trusted-list snapshot and can be verified offline with open-source software is easier to defend than a PDF that merely says 'timestamped'.
The UK and courts outside the EU
The UK kept its own version of eIDAS after Brexit. In the UK text, Article 41(1) and (2) remain, but paragraph (3) on recognition across member states was omitted with effect from 31 December 2020. Whether a stamp from an EU qualified provider counts as qualified before an English court is therefore a question for your counsel; do not assume the EU presumption travels.
Outside the EU the stamp still has real value as technical evidence: an independent, signed and verifiable record that the data existed at a given time. Present it with a short verification note explaining how anyone can check it, instead of relying on the word qualified alone.
A practical setup for firms and compliance teams
If web pages, posts or documents regularly end up in your files, decide once how they will be timestamped:
- GetProofAnchor web app: every proof on a paid plan carries a qualified eIDAS timestamp from an EU-listed qualified trust service provider; the Evidence ZIP includes the trusted-list snapshot and verifies offline with the open-source gpa-verify. From 9 € excl. VAT for 3 proofs (10.89 € incl. 21 % VAT); Business at 99 € a month excl. VAT covers 400 proofs, 10 users and case folders.
- Forensic Browser: a Windows app for multi-page sessions, logged-in pages, video and files, with a PDF that embeds a qualified document timestamp (PAdES) and validates in Adobe Acrobat Reader. Annual licences from 290 € excl. VAT.
- Assisted Capture: our operator captures the URLs for you and sends the evidence package, from 49 € excl. VAT (59.29 € incl. VAT); Rush with a guaranteed 60 minutes costs 249 € excl. VAT.
- Browser-extension captures are sealed on receipt: the qualified stamp proves integrity and the time we received the capture, not independent observation. Where that matters, use a server capture, Forensic Browser or Assisted Capture.
Whatever tool you use, keep the original package rather than just the PDF report, and note in the file how the timestamp can be verified. To see a qualified-timestamped package before deciding, send one URL to sales@getproofanchor.com and we will capture it as a free sample and send you the evidence package.
FAQ
Is a non-qualified timestamp admissible in court?
Does a qualified timestamp prove that a website really showed this content?
Is a blockchain timestamp a qualified timestamp?
How long does a qualified timestamp stay verifiable?
Can I timestamp an old screenshot now?
Sources
- Regulation (EU) No 910/2014 (eIDAS), Articles 41 and 42 – EUR-Lex
- Regulation (EU) 2024/1183 amending eIDAS – EUR-Lex
- Implementing Regulation (EU) 2025/1929 on qualified electronic time stamps – EUR-Lex
- UK retained eIDAS, Article 41 – legislation.gov.uk
- ETSI – EU trusted lists common scheme rules
- European Commission – eSignature FAQ (trusted lists, validation)
For lawyers and legal teams
Evidence the other side can’t easily dismiss
Forensic web capture with an eIDAS qualified timestamp, Bitcoin anchor and an offline-verifiable Evidence ZIP — methodology designed with reference to ISO/IEC 27037. File it as a data package and a PDF report.
Related guides
-
eIDAS Article 41: what a qualified timestamp presumesThe presumption in detail
-
eIDAS Article 42: is your timestamp really qualified?Six checks of the requirements
-
Are blockchain timestamps qualified under eIDAS?OpenTimestamps and the law
-
Verify a proofCheck an evidence package yourself
-
Forensic BrowserPAdES PDF that validates in Adobe Reader
-
PricingFrom 9 € excl. VAT for 3 proofs
A qualified timestamp on every proof
Capture a page from your browser or by URL and get an evidence package with a qualified eIDAS timestamp that anyone can verify offline.
From 9 € excl. VAT (10.89 € incl. VAT) for 3 proofs. No trial; a free sample proof is available on request via sales@getproofanchor.com.