Skip to main content

Qualified Timestamp Server: Prove When Your Data Existed

Updated: November 17, 2026

Netlock is an EU qualified trust service provider and issues qualified timestamps with ECC and RSA 4096 algorithms. Buy any quantity for Adobe Acrobat or your own systems; in the Netlock app, every signature gets one automatically.

Get qualified timestamps

Package prices are shown in the app. Any quantity: the more you buy, the cheaper each timestamp.

Larger volumes or custom needs, such as an SLA

A timestamp server, run by a timestamping authority (TSA), returns a signed timestamp for your document’s hash: evidence that the document existed at that moment. A qualified timestamp comes from a qualified trust service provider, and eIDAS presumes the accuracy of its date and time and the integrity of the data it is bound to.

What Is a Timestamp Server?

A timestamp server is the online service of a timestamping authority (TSA): it receives a hash of your data and returns a timestamp, signed by the authority, that binds the data to a point in time. You will also see the terms timestamp server, timestamp authority and trusted timestamping.

The EU’s eIDAS Regulation (Regulation (EU) No 910/2014, as amended by Regulation (EU) 2024/1183) 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)). On the technical side, RFC 3161, the Time-Stamp Protocol (TSP), describes how software asks a TSA for a timestamp and what comes back. In the standard’s words, the TSA provides “a ‘proof-of-existence’ for this particular datum at an instant in time”. Netlock issues timestamps under RFC 3161.

A file’s date or an email’s time is recorded by the system that created or stores it, so it is only as trustworthy as that system. A timestamp comes from a trust service provider acting as a third party, and it is bound to the data cryptographically: if the document changes by a single character, verification shows it.

A timestamp does not show who accepted a document; that is what an electronic signature is for. It shows when the document existed. Together they show who signed the document and when. Our article on why timestamps matter explains why trusted time has become evidence in its own right.

What Is a Qualified Timestamp Under eIDAS?

A qualified timestamp is an electronic timestamp that meets the requirements of eIDAS Article 42, and the difference from other timestamps is its legal effect. Any electronic timestamp can serve as evidence: it “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” (Article 41(1)).

The qualified timestamp gets a presumption on top of that: “A qualified electronic time stamp 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” (Article 41(2)). To be qualified, it must meet Article 42(1):

  • (a) “it binds the date and time to data in such a manner as to reasonably preclude the possibility of the data being changed undetectably”;
  • (b) “it is based on an accurate time source linked to Coordinated Universal Time”; and
  • (c) “it 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”.
Electronic timestampQualified electronic timestamp
Who issues itAny trust service provider, also without qualified statusA qualified trust service provider, which you can look up in the EU trusted lists
RequirementsNo specific requirements like those in Article 42 (Article 3(33))Article 42(1): it reasonably precludes undetectable change, uses an accurate time source linked to UTC, and is signed or sealed by the provider
Legal effectCannot be denied legal effect or admissibility as evidence only because it is electronic or not qualified (Article 41(1))Presumption of the accuracy of the date and time and of the integrity of the data (Article 41(2))
Recognition in the EUNo EU-wide recognition ruleRecognised as a qualified timestamp in all other member states (Article 24a(6))

Netlock provides qualified timestamping: the timestamps you buy from us and those on signatures made in the Netlock app are qualified.

When Do You Need a Timestamp?

You need one when you may later have to prove when a document or data existed, and whenever a law requires one. These are the typical cases:

  • To prove a signature was made while the certificate was valid. When a qualified electronic signature is validated, one of the conditions is that its signing certificate “was valid at the time of signing” (eIDAS Article 32(1)(b)). A timestamp shows that the signature was made before the certificate expired or was revoked. RFC 3161 gives this as its own example: to verify “that a digital signature was applied to a message before the corresponding certificate was revoked”.
  • To prove data existed, without a signature. With research data, technical documentation, log files or a given version of some content, the question is often not who approved it, but when it existed and in what state. RFC 3161 also names indicating “the time of submission when a deadline is critical”.
  • When the law requires it, as Hungarian law does in some cases (below).

Timestamping is typically used by organisations that have to prove the time of many documents or transactions: banks, insurers, brokerage firms, clearing houses, online trading platforms, electronic marketplaces, archiving companies and e-invoicing businesses.

If Hungarian Law Applies to Your Document

Hungarian law is official only in Hungarian, so the quotes below are our translation.

  • Under the Hungarian Code of Civil Procedure (Pp., Act CXXX of 2016), a private document has full probative value if the signer placed their qualified electronic signature or seal, or their advanced one based on a qualified certificate, on the electronic document “and – where a law so provides – places a time stamp on it” (section 325(1)(f)).
  • Under the Hungarian Digital State Act (Dáptv., Act CIII of 2023), unless a law provides otherwise, an electronic private document is one that the declaring party “provides with at least the signature defined in point 23 of section 8 [an advanced electronic signature] and an electronic time stamp, or authenticates with eAláírás” (section 109(1)). eAláírás is the signature of the Hungarian government’s DÁP mobile app. A legal declaration made in such a document also counts as made in writing under section 6:7(2) and (3) of the Hungarian Civil Code (Ptk., Act V of 2013).
  • If there is doubt about the data certified by a timestamp attached to an electronic document, “the court primarily contacts the trust service provider that performed the time-stamping” (Pp. section 325(7)).

How Does a Timestamp Server Work?

The timestamp server never needs to see your document: its hash is enough. The steps:

  1. Hash. Your software, such as a signing app, a document management system or an invoicing system, computes a short fingerprint (hash) of the document. The document’s content cannot be reconstructed from the hash, in whole or in part.
  2. Request. Your software sends the hash to the timestamp server in a timestamp request. Netlock issues timestamps under RFC 3161, where the request carries the hash of the data instead of the data itself.
  3. Time. The authority adds the date and time to the hash. For a qualified timestamp, the time must be “based on an accurate time source linked to Coordinated Universal Time” (eIDAS Article 42(1)(b)).
  4. Signature. The authority signs the hash and the time with its advanced electronic signature or advanced electronic seal and sends the result back: that is the timestamp, which RFC 3161 calls a time-stamp token.
  5. Verification. Your software stores the timestamp in the signature or next to the document. When it is checked, the hash is computed again: if the document has changed since, the two hashes don’t match.

How Do You Get a Timestamp Server URL?

You buy timestamps in the Netlock app and get your own timestamp server URL to set in your software. If you only need timestamps on the signatures you make in the Netlock app, you don’t need a URL at all.

Timestamps for Your Own Systems

If you want timestamps in your own application, document management or invoicing system, or in a signing program such as Adobe Acrobat Reader, you buy them as a package:

  1. Register or log in to the Netlock app. Timestamping is set up for an organisation: if you don’t have one in the app yet, create one. Creating an organisation is free, and timestamping needs no authorisation by its legal representative.
  2. Choose the quantity and pay in the app’s catalog, under Timestamping, where you see the current package prices. You can buy any quantity, and the more you buy, the cheaper each timestamp.
  3. Get your own timestamp server URL, which contains your unique identifier. Treat it like a password: it carries your access credential, so keep it out of logs, tickets and source code.
  4. Set the URL in your software. From then on, it requests qualified timestamps from Netlock.

You buy exactly as many timestamps as you need. For larger volumes, talk to sales; for custom needs, such as a service level agreement (SLA), we make a custom offer.

Get qualified timestamps

Package prices in the app

Signing in the Netlock App

When you sign a document in the Netlock app, you don’t order timestamps separately: every signature gets a qualified timestamp. All signatures in Netlock are in PAdES Baseline LTA format, and the qualified timestamp comes from our own qualified timestamping service, so the signature can still be validated years later.

The app and the qualified certificate are free, and you get 15 free signatures; after that, you buy credits, and one signature is 1 credit. You have a working qualified electronic signature 1 minute after you register, and you can sign on your phone too. See how to sign a PDF.

How to Add a Timestamp to a Signature in Adobe Acrobat

Set your timestamp server URL once in Adobe Acrobat Reader, and Acrobat adds a timestamp to your signatures from then on. Following Netlock’s Adobe guide:

  1. Open Preferences and select the Signatures category.
  2. Under Document Timestamping, select More….
  3. Under Time Stamp Servers, select New.
  4. In Name, enter any name, for example “Netlock qualified timestamp”, and paste your own timestamp URL into Server URL. Leave “This server requires me to log on” unticked.
  5. Select OK, then Set Default to make it your default timestamp server.

After you sign, open the signature panel: the signature properties show whether the signature is valid and whether the timestamp was added. If you can’t find a timestamp URL you received earlier, call our customer service on +36 1 255 0792.

How Do You Verify a Timestamp?

You verify a timestamp through the authority’s signature on it: whether the signature or seal with which the authority issued the timestamp is valid, and whether its certificate chain leads to a trusted root. For a signed PDF, your validation software does this for you. In Adobe Acrobat Reader:

  1. Open the signed PDF, then the signature panel.
  2. In the signature properties, check that the signature is valid, when it was made and that the timestamp was added.
  3. Check who issued the timestamp. A Netlock qualified timestamp chains up to one of Netlock’s qualified timestamping CAs on the Hungarian trusted list, such as “NETLOCK Trust Qualified TSA ECC CA” or “NETLOCK Trust Qualified TSA RSA 4096 CA”, with the organisation “NETLOCK Kft.”.
  4. Check that the certificate chain is valid up to the root, and that the issuer is on the EU trusted lists.

Adobe Acrobat Reader checks qualified certificates against trust lists, so Netlock’s guide recommends turning on the Adobe Approved Trust List (AATL) and EU Trusted Lists (EUTL) downloads in the Trust Manager and updating both.

Why Netlock

Netlock is a qualified trust service provider on the EU Trusted List, where its entry shows qualified timestamping. In Hungary, the National Media and Infocommunications Authority (NMHH) supervises trust services (Dáptv. section 95(1)), and you also find Netlock in the NMHH register. See our qualified trust service provider page for the details.

What you get:

  • Qualified timestamps, with the presumption of eIDAS Article 41(2), recognised as qualified in every EU member state.
  • Standard access: RFC 3161 timestamps through your own timestamp server URL.
  • Confidentiality: a timestamp request carries only your document’s hash, not its content.
  • ECC and RSA 4096: we issue qualified timestamps with both; both services are on the Hungarian trusted list. The service in the app’s catalog uses ECC; for RSA 4096 timestamps, talk to sales.
  • Any quantity: package prices are shown in the app, and the more you buy, the cheaper each timestamp.
  • A timestamp on every signature: every signature you make in the Netlock app gets a qualified timestamp.
  • Published rules: the policy of the qualified timestamping service is published among Netlock’s policies.

FAQ

Your own: after you pay, you get a timestamp server URL with your unique identifier, and you set it in your software. Keep it secret, because it carries your access credential. If you can’t find a URL you received earlier, call our customer service on +36 1 255 0792.

You can start for free in the Netlock app: registration and the qualified certificate are free, and you get 15 free signatures, each with a qualified timestamp. Standalone timestamps for your own systems are paid.

The current package prices for timestamps in your own systems are shown in the Netlock app. You can buy any quantity, and the more you buy, the cheaper each timestamp. For larger volumes, talk to sales; for custom needs, such as an SLA, we make a custom offer. If you sign in the Netlock app, every signature gets a qualified timestamp and one signature is 1 credit; your first 15 signatures are free. Current credit prices are on our pricing page.

Not always, but some laws require one, and it helps you prove when you signed. The eIDAS definition of a qualified electronic signature (Article 3(12)) does not mention a timestamp. Under Hungarian law, a private document with full probative value also needs a timestamp “where a law so provides” (Pp. section 325(1)(f)), and an electronic private document needs at least an advanced electronic signature and a timestamp, or eAláírás, unless a law provides otherwise (Dáptv. section 109(1)). A timestamp also shows that the signature was made before the certificate expired or was revoked. In the Netlock app, every signature gets a qualified timestamp.

Not when you request timestamps from your own system. The request carries only the document’s hash, and the content cannot be reconstructed from the hash, in whole or in part. So you can timestamp confidential documents too.

Yes. “A qualified electronic time stamp provided in one Member State shall be recognised as a qualified electronic time stamp in all other Member States” (eIDAS Article 24a(6)).

Code-signing tools, such as Microsoft SignTool, also request RFC 3161 timestamps from a timestamp server URL. Talk to sales to check your set-up before you buy.

As long as the timestamp can be verified and the cryptographic algorithm used to sign it stays strong. Once the timestamp’s validity ends, the time of signing can no longer be established reliably, and if the algorithm weakens, the document’s authenticity is no longer assured either. A new, so-called archive timestamp added before that preserves the authenticity of the earlier signatures and timestamps while it is itself valid, so long-term archives repeat archive timestamping from time to time. Our article Will Your Electronic Signature Still Be Valid in Ten Years? explains the background. Our guide to electronic archiving covers the rules for keeping documents.

Qualified timestamps for your own systems, with your own timestamp server URL and in any quantity, or automatically on every signature in the Netlock app.

Get qualified timestamps

Package prices in the app; the more you buy, the cheaper each timestamp

Sign up for free

Pricing

Tell Us What You Need to Prove

We’ll show you the fastest way to start, from one workflow to an organisation-wide proof layer.

Sign up for free