eIDAS Article 41: what the qualified timestamp presumption covers, and what it doesn't

The short answer

A qualified electronic timestamp is presumed to show the correct date and time, and the data it is bound to is presumed not to have changed since that moment. That is the whole presumption under Article 41(2) of Regulation (EU) No 910/2014 (eIDAS).

It does not presume that the content is true, who created it, or that a captured web page shows everything a visitor saw. Those questions are answered by the evidence you build around the timestamp: the capture method, the artifacts and the documentation.

What Article 41 actually says

Article 41 has three paragraphs, and each does a different job:

• Article 41(1): an electronic timestamp may not be denied legal effect or admissibility as evidence solely because it is electronic or because it is not qualified. A simple timestamp is not worthless; it simply carries no statutory presumption.
• Article 41(2): 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 that date and time are bound.
• Article 41(3): a qualified electronic timestamp issued in one Member State is recognised as a qualified electronic timestamp in all Member States.

The amending Regulation (EU) 2024/1183, often called eIDAS 2, did not rewrite this legal effect. Its changes concern how qualified trust services are supervised and specified, not what a qualified timestamp presumes.

What the presumption covers

Read the wording closely. The presumption attaches to two things only:

• Time: the date and time in the token are presumed accurate. Article 42 requires the time source to be linked to Coordinated Universal Time.
• Integrity: the data bound to that time, in practice a hash of a file or a set of files, is presumed unchanged since the timestamp was issued.
• Cross-border effect: through Article 41(3), the same qualified status applies before courts and authorities in every Member State, without re-qualification.

What the presumption does not cover

This is where most overstatements happen. A qualified timestamp says nothing on its own about:

• Truth of the content: a timestamped defamatory post is presumed to have existed in that form at that time, not to be accurate.
• Authorship and identity: the token does not say who wrote the content or who operated the account.
• Completeness of a web capture: whether the capture shows what a particular visitor saw depends on the capture method, not on the timestamp.
• Events before the timestamp: it proves the data existed no later than the stamped time. It does not prove when the data was first created or published.

So the presumption is strong on the question of when and whether it changed, and silent on the question of what it means. Treat it as the anchor of an evidence package, not as the whole package.

Qualified or not: what Article 42 requires

Only a qualified electronic timestamp carries the Article 41(2) presumption. Article 42 sets the requirements:

• It binds the date and time to the data in a way that reasonably precludes undetectable change.
• It is based on an accurate time source linked to Coordinated Universal Time.
• It is signed with an advanced electronic signature or sealed with an advanced electronic seal of the qualified trust service provider, or by an equivalent method.
• It is issued by a qualified trust service provider with qualified status for timestamping, which you can check in the EU Trusted Lists.

In practice qualified timestamps follow RFC 3161 and the ETSI standards for timestamping (EN 319 421 and EN 319 422). A timestamp from a non-qualified service, a server log or a blockchain transaction can still be evidence under Article 41(1), but the court weighs it freely, without the presumption.

How the presumption plays out in a dispute

A presumption shifts the burden. If you submit data with a valid qualified timestamp, you do not have to prove that the time is right or that the file has not been altered since. The party that disputes it has to bring something concrete, for example evidence that the provider did not hold qualified status at that time or that the verification fails.

Two practical consequences follow. First, verification must be possible for the judge, the expert and the other side, ideally without trusting the vendor that produced the evidence. Second, the arguments simply move elsewhere: to how the content was captured, whether anything was left out, and whether the captured page is the relevant one. Those are the weak spots your documentation has to close.

Czech practice: free evaluation of evidence

This paragraph concerns Czech law specifically. In Czech civil proceedings the court evaluates evidence at its own discretion (section 132 of the Code of Civil Procedure, Act No. 99/1963 Coll.). The eIDAS Regulation applies directly, so the Article 41(2) presumption applies to qualified timestamps as such, while everything outside it, such as the capture method, completeness and context, is assessed freely by the court. A well-documented capture therefore matters as much as the timestamp itself.

Checklist: making the presumption work for web evidence

• Use a qualified timestamp from a provider listed in the EU Trusted List, and keep the timestamp token itself, not only a PDF that mentions it.
• Timestamp hashes of all relevant artifacts (screenshot, HTML, network log, video), not only an image.
• Record how the capture was made: browser, settings, consent clicks, any visual interventions.
• Prefer a capture made by independent infrastructure or a documented forensic process over a screenshot from your own device.
• Make offline verification possible: include the trust list data and a verification method that does not depend on the vendor.
• Capture before you report or send a letter. Once the other side is warned, content tends to change or disappear.

Where GetProofAnchor fits

GetProofAnchor binds every artifact of a capture (screenshot, HTML, MHTML, HAR, video, TLS certificates and capture metadata) by SHA-256 into a qualified electronic timestamp (RFC 3161) from SK ID Solutions, an EU qualified trust service provider. Any change to a sealed artifact after the timestamp is detectable offline with open-source tooling (gpa-verify), using the EU Trusted List snapshot included in the evidence ZIP. Three ways to use it:

• Web app: server-side capture by URL, plus the browser extension for logged-in pages on Enterprise and Business (captured on your device, sealed on receipt); from 9 EUR excl. VAT for 3 proofs (10.89 EUR incl. VAT) or monthly plans from 19 EUR excl. VAT (22.99 EUR incl. VAT).
• Forensic Browser: a Windows app for multi-page or logged-in sessions, producing a PAdES PDF that validates in Adobe Acrobat Reader or a ZIP for experts; annual licence from 290 EUR excl. VAT (350.90 EUR incl. VAT).
• Assisted Capture: we capture the URLs for you and send the evidence package by e-mail; from 49 EUR excl. VAT (59.29 EUR incl. VAT), with a 60-minute guaranteed Rush tier.

None of this guarantees how a court will rule. It gives you the Article 41(2) presumption on time and integrity, plus a documented capture method for everything the presumption does not cover.

FAQ

Sources

• Regulation (EU) No 910/2014 (eIDAS), Articles 41 and 42
• Regulation (EU) 2024/1183 amending eIDAS
• EU Trusted Lists browser (European Commission)
• RFC 3161: Time-Stamp Protocol (TSP)
• Czech Code of Civil Procedure, Act No. 99/1963 Coll., section 132