Digital Product Passports, at stable product addresses.

Overview

A Digital Product Passport is a structured record about a specific product. For it to be useful years after the product was sold, it needs an address that belongs to the product rather than to a shop, a campaign or a webpage.

That is what this domain does. A code printed on a product carries an identifier. dppcode.org takes that identifier and sends the reader to the passport published for it. The identifier and the passport are deliberately separate, so that where a passport is served can change without any printed code becoming wrong.

This domain is operated by Signal (section 15). Everything on this page is written to be checked, not believed: where a claim can be inspected, the place to inspect it is linked.

What a Digital Product Passport is

A structured record of what a product is made of, where it was made and what can be done with it at the end of its life. It is published by the business placing the product on the market, and reachable at an address tied to the product itself.

In the European Union, passports are introduced by the Ecodesign for Sustainable Products Regulation, which sets out a framework and then applies it to individual product groups through separate rules made under it. What a passport must contain, and from when, therefore depends on the product group. This page describes how this resolver works; it is not legal advice, and the official sources are linked in section 10.

What a passport contains

Depending on the applicable product rules, a passport published through this resolver may carry:

• Product identity: what the product is, and the identifier this address is built from.
• Composition: materials and their proportions.
• Origin and manufacturing: where it was made, and by whom, where that has been established.
• Environmental information: calculated figures, labelled as calculated (section 09).
• Care and repair: how to keep it in use.
• End of life: recycling and disposal information.
• Evidence: for each fact, where it came from (section 07).

Not every category applies to every product or every regulatory phase. Where something has not been established, the passport says so instead of leaving it out silently (section 08).

How dppcode.org works

The printed code carries an identifier and nothing else. This domain resolves that identifier and redirects to the passport resource. It does not serve the passport at the identifier's own address.

1. OnePrinted code A QR code or link on the product or its label.
2. TwoIdentifier The code carries an identifier, not a page.
3. ThreeThis resolver dppcode.org looks it up and redirects.
4. FourThe passport The published record for that product.

That separation is the point: a passport can move without a printed code becoming wrong. An identifier that has never been published returns a plain 404 saying exactly that, never an empty or invented record.

Product identifiers

Two kinds of address exist here and the difference is deliberate.

/01/<gtin>Where the product has a usable GTIN

The address follows the GS1 Digital Link convention: /01/ followed by the GTIN, where 01 is the GS1 application identifier meaning that a GTIN follows.

/id/<identifier>Where it does not

An identifier is issued here instead, on /id/. An identifier issued here is not a GS1 key and is not presented as one. The path segment is deliberately not a number so that no reader or parser can mistake it for one, and the passport records that the product has no GTIN.

Where a GTIN is used it is the one the seller holds in their own records. Publishing at that address is not a check that the seller is the party GS1 issued the number to, and this implementation does not make that check.

Evidence and provenance

The governing principle is that a value should not appear as an unexplained fact. Each fact in a passport carries what it was established from, so a reader can judge it without taking it on trust.

Depending on the fact, that may be the seller's own product records, a document they supplied, a public register or a structured calculation over inputs that are themselves recorded. Where two credible sources disagree, the disagreement is shown, not settled in favour of whichever produces a fuller passport.

Unknown information

Unknown is not zero. Unknown is not false. Unknown is not a plausible default.

Where information has not been established, the passport identifies that state and does not manufacture a value. It is not filled with an industry average, an assumed figure or an empty field that reads as an answer.

The reason is that a value nobody can trace cannot be checked by anyone: not a customer, not an auditor, not the seller. Naming what is outstanding is also what makes it possible to go and establish it.

Modelled information

Some values, environmental figures in particular, are calculated from declared inputs instead of measured. Where that is the case the passport identifies the figure as modelled, names the model or dataset it came from, and, where the calculation can be reproduced, links to the calculation itself.

A modelled figure is not a measurement and is not presented as one. Reproducibility is not the same as independent certification, and nothing here is claimed to be independently certified.

Regulatory framework

The sources below are separated by what they are. Law, official infrastructure, technical standards and choices made in this implementation are different things, and mixing them is how an implementation detail comes to sound like a legal requirement.

Regulatory and standards references above reviewed September 2026. The official sources are linked directly so they can be checked as they stand today, not as summarised here.

For regulators and auditors

An index to what you are most likely to be looking for.

• Who operates this domain Operator identity and public contact.
• The resolver description Published at the location the GS1 resolver standard specifies, so the claim can be checked and not taken on trust. It does not name the operating company; the company is named in section 15.
• How identifiers are formed Including what this implementation does and does not verify.
• How facts are supported Provenance, and what happens when sources disagree.
• How unknowns are handled How unavailable or unestablished information is represented.
• How modelled values are marked And what is not claimed about them.
• Law, standards and implementation choices, separated With links to the official sources.
• Public routes The addresses this domain answers.

For businesses

If you sell a product whose passport is published here, the practical shape of it is:

• Each of your products gets an address on this domain, built from its identifier.
• What the passport says comes from your own product records, evidence you supply and public registers, with each fact carrying where it came from.
• Where something has not been established, the passport shows the gap instead of filling it. Closing it is a matter of supplying the evidence.
• Signal publishes and resolves. It does not take on your obligations as an economic operator. Duties placed on economic operators by the applicable rules, including registration with the European Commission's Registry, are not discharged by publishing here (section 10).

For technical integrators

This resolver publishes a description of itself at /.well-known/gs1resolver, which is the location the GS1 resolver standard specifies. It gives the resolver root, the primary keys answered for and the link type vocabulary used. That document, not any label on this page, is what makes the resolver's behaviour checkable.

Only the GTIN key (01) is claimed. A resolver that lists a key it cannot answer for returns nothing where a client was told to expect an answer.

A client that wants the machine-readable index of links for an identifier, not the passport, can request it with ?linkType=linkset or by sending Accept: application/linkset+json. It is never the default: the default for somebody scanning a product is the product.

Public routes

An identifier that has not been published returns 404 with a plain statement to that effect. An address that is not a valid identifier returns 400.

Operator

This resolver is operated by SIGNALANALYTICS.AI LTD (Signal), a company registered in the United Kingdom, which builds systems that turn a seller's product information, the evidence they provide and relevant public records into structured passport records.

Signal does not manufacture or sell the products whose passports are published here, and operating this resolver does not make Signal the economic operator for any of them. Responsibility for a product's information, and for the passport obligations that attach to it under the applicable rules, sits with the relevant economic operator. Signal's part is to establish what can be established from those sources, to be explicit about what has not been and to serve each passport at a stable address.

Contact

Questions about this resolver, about a particular passport or from a regulator or auditor: passports@dppcode.org

Further reading

Plain explainers on ActivateDigital, the website of the company that operates this resolver. They describe the rules and how passports work; they are not legal advice.

• What happens when you scan the code The layers between a code on a product and a passport on a screen
• What a Digital Product Passport has to hold, by product Digital Product Passport requirements by product category
• What a GS1 Digital Link is GS1 Digital Link, what resolves it and how it carries a passport
• The three identifiers a passport needs Product, operator and facility identifiers
• What happens to a passport if its company stops trading When the link dies
• The EU passport registry, and what it does not do The EU DPP Registry is live. What does your business still need to do?
• What a textile passport is What is a textile Digital Product Passport?
• What a battery passport is, and from when Battery Digital Product Passport requirements
• Which passport dates apply when Digital Product Passport timeline
• An example passport, row by row An annotated textile Digital Product Passport
• Where do I start with a Digital Product Passport? Scope, then identity, then data, then evidence