How dpp-backup.com keeps a passport available
Your passport platform sends every published passport to dpp-backup.com through EN 18222. Each version is stored as it was received, with a signed receipt. If your own host can no longer serve a passport, the copy can answer at the same address.
1. Your platform sends each published passport
The platform that hosts your passports is connected to dpp-backup.com once. From then on it sends each passport when it is published, and again every time it changes.
It uses two calls of EN 18222, the European standard for passport interfaces: CreateDPP for a new passport and UpdateDPPById for a change. EN 18221 4.5 names this interface as one way to replicate a passport to its back-up provider.
Only published passports are backed up. A draft is refused.
2. Every version is kept
Each change becomes a new version. Every version is stored whole, as it was received, and is never changed afterwards. Nothing can be deleted through the interface your platform uses.
That is what EN 18221 asks of a back-up provider: to keep every archived version for the lifetime of the passport (4.2), and the newest version with every required historical version (4.3).
3. A signed receipt for every version
For each stored version, dpp-backup.com signs a receipt. It says which passport, which version, the SHA-256 hash of its content and when it was received. Your platform gets the receipt in the answer to its call.
Anyone can check a receipt against the public key. The verify page does it in your browser.
- Passport
5b1d3a8e-0c3f-4a8e-9a77-2f1f3c9b7e01- Version
3- Content hash (SHA-256)
5ef66f44fdc06ae36600e5034d550dd9fd3fa77f223f4e6cd292607cba1d1c42- Received at
2026-11-20T09:14:02.318Z- Sender
conn-d7e4ebf8-eac6-48b7-b79f-27487a59d7a0- Receipt id
bb0fed2c-d3b6-4864-803d-bfa4a373d142- Key id
e1e440dafc6d9fc4
4. You see it in the portal
In the portal you see your passports and every version of each. You can open the version that was current on a given date, compare two versions and export what is held.
5. When your host cannot answer
A passport is reached through the address in its QR code. If the host behind that address stops answering, the domain can be pointed at dpp-backup.com. The same addresses then answer from the copy, and the page says that it is the back-up copy.
You prove in the portal that the domain is yours, with a DNS TXT record. Answering for the domain from the copy needs two people in your organisation: one asks, another approves. dpp-backup.com then opens the copy for reading on that domain.
This matters because ESPR Article 11(e) asks the passport to stay available after an insolvency, a liquidation or the end of activity in the EU.
6. Who can read the copy
EN 18221 4.3: the copy keeps the access restrictions of the original passport. Specifically authorised users can read it while your passport is live; general access opens once the economic operator has left the market.
- To do that, the copy needs to know which data elements are not public. Your platform sends that list with each version, and those data elements are never shown to the public from the copy.
- Without the list we show no product data from that version publicly rather than guess, so make sure your platform sends it.
- Public reading is opened for a domain only when that domain is pointed at the copy.
What dpp-backup.com does not do
- It does not create or edit passports. Your platform does that.
- It does not keep drafts.
- It does not put your platform back to an earlier state. It holds every version, and each one can be read.
Keep a back-up copy of your passports
Create an organisation with your company email. Once it is approved, you connect the platform that holds your passports.
A company email address is required. Our staff review new organisations on working days. The portal is in English.