RFC 3161 timestamp server →
Every CodeB installation has its own timestamp authority endpoint with its own responder certificate.
TimeNotary · now part of CodeB
TimeNotary is now part of CodeB: trusted timestamps inside your signing platform
Aloaha TimeNotary issued RFC 3161 timestamps that prove when a document existed, when a transaction happened and when a signature was applied. Today this is part of CodeB: every CodeB installation runs its own RFC 3161 timestamp server, next to PDF signing, an OCSP responder and remote signing – in your own installation in the EU, without third-party trackers.
In one sentence: TimeNotary’s RFC 3161 timestamping now lives in CodeB – run it in your own installation, use it for long-term valid PDF signatures, or forward to a public timestamp authority for documents that others must trust.
RFC 3161 · PAdES B-T / B-LT / B-LTA · RFC 6960 OCSP · Cloud Signature Consortium API v2
In short
- What it was
- Aloaha TimeNotary: an RFC 3161 timestamping service, run as your own server, hosted for you or used online.
- Where it is now
- In CodeB: a timestamp server in every installation, used by the CodeB signing services.
- Why timestamps
- A timestamp proves that a document or signature existed at a given time and has not changed since – so a signature can be checked long after the signing certificate has expired.
- Where it runs
- In your own CodeB installation in the EU, or hosted for you by Aloaha. Only hashes are timestamped, never the document.
Where TimeNotary lives now
Signed PDFs that stay valid →
PAdES signatures with timestamps (B-T), validation data (B-LT) and archive timestamps (B-LTA).
OCSP responder →
Certificate status for CodeB signing certificates, as RFC 6960 answers.
Remote signing →
Signing through the Cloud Signature Consortium API v2, confirmed in CodeB Wallet.
Sign PDFs with CodeB Wallet →
Sign with the wallet on the phone or with your own signature card over NFC.
Audit-proof invoices →
Signed and timestamped e-invoices for long-term archiving.
Honest scope
The timestamp server in a CodeB installation signs with its own certificate. It is not a qualified trust service: its timestamps are admissible as evidence (eIDAS Art. 41) but do not carry the legal presumption of qualified electronic timestamps (Art. 42). For documents that others must trust, CodeB forwards timestamp requests to a public timestamp authority of your choice.
Frequently asked questions
What happened to TimeNotary?
TimeNotary’s RFC 3161 timestamping is now part of CodeB. The timestamp server ships with every CodeB installation and is used by the CodeB signing services.
Are the former TimeNotary products still offered?
No. Timestamp packages, the stand-alone timestamp server licence and the hardware security module of the former TimeNotary site are no longer offered. Timestamping is part of CodeB.
I use a TimeNotary timestamp URL. What should I do?
Write to info@aloaha.com. We help you move to the timestamp server of a CodeB installation or to a public timestamp authority.
Are CodeB timestamps qualified?
No. The CodeB timestamp server is not a qualified trust service. For qualified timestamps, CodeB forwards to a public timestamp authority of your choice.
Timestamps and signatures for your organisation?
Write to us: we show you timestamping and signing in CodeB and help you move from TimeNotary.