XProduct
Free check · no account needed

Is this passport the real one? Check its seal.

Passports from xProduct carry a digital seal in their standard answers. Check it here and you see whether the data is exactly what xProduct sealed for that passport, or whether it was changed since. That works for the live passport and for a signed .jws copy someone saved and passed on.

The check runs in your own browser, with the public keys of this site. A valid seal shows the data is unchanged; it does not say the product meets the law.

Seal header · decoded

Echoes of the Wildwood Embroidered Backpack

algMethod
ES256
kidKey used
ee483d2e…439a
issSite that sealed it
https://xproduct.co.uk
subPassport
https://xproduct.co.uk/public/product/5905
xp_operatorEconomic operator (GLN)
5070004750503
xp_sealedBySealed by xProduct
platform
iatWhen it was sealed
1794387600
The real seal of the UK passport 5905, read on 11 November 2026. The key id changes when a new key is brought in.

Check now/Runs in your browser

Check a passport seal

Type the product number or the passport address of a passport on this site, or upload a signed passport file (.jws) that someone gave you.

A passport on this site

Its product number, or its passport address.

A signed passport file

A .jws file, e.g. from /api/dpp/{number}/en18223/signed.

This page checks passports and seals of xproduct.eu. A passport from xproduct.co.uk has its own key: check it on xproduct.co.uk/passport-seal.

Signature method: a JSON Web Signature (RFC 7515)
ES256
where the check runs, with the site's public keys
Your browser
needed to check a passport or a file
No account
each site seals with its own key
UK + EU

01/What a seal is

A digital signature on the passport data

When xProduct gives out a passport in the standard format, it signs the exact data with a private key. Anyone can check that signature with the matching public key. If even one character of the data changes, the check fails. That makes the passport tamper-evident: a change cannot be hidden.

  • A signature, not a picture

    The seal is a JSON Web Signature (RFC 7515) made with ES256. It is checked with maths, not by looking at a logo.

  • Made by xProduct, for the operator

    xProduct seals the passport as the platform that holds it, on behalf of the company named in it as economic operator.

  • It travels with the data

    Save the signed file, send it on, check it later. The seal stays with the data wherever the copy goes.

  • Tamper-evident, not secret

    The seal does not hide or lock the data. It shows whether the data is still the same as when it was sealed.

Whose seal is it?

Today it is xProduct's platform seal, made for the economic operator named in the passport. It is not yet the operator's own qualified electronic seal; that step waits on the EU rules for passport seals. The private key never leaves a cloud key vault: the signing happens inside the vault.

02/When to use it

Whenever a passport has passed through other hands

The live passport behind a QR code is read straight from xProduct. The seal matters most when the data reaches you another way: as a file, through another system, or months later.

  • Buyer

    Before you rely on a passport

    A supplier sends passport data with an offer or a delivery. Check it is the data xProduct holds for that passport, unchanged.

  • Customs · market surveillance

    When a copy is handed over

    A passport file is handed over during an inspection or comes from another system. The seal shows whether it was changed on the way.

  • Auditor · certifier

    For your audit file

    Keep the signed file with your notes. Months later you can still show the data you looked at was the data xProduct sealed. Keep a copy of the public key set (/.well-known/jwks.json) with it, so the check still works after a key change.

  • Anyone with a saved copy

    A copy saved months ago

    Old copies can be checked while the key that sealed them is still listed. Kept a copy of the public keys too? Then you can check it at any time, offline.

03/How to check

Three steps, under a minute

You need the passport's number, its address or a signed file. No account and no software.

  1. Find the passport

    Open the passport page (scan the QR code and let it open), then copy the address from the browser. It ends in /public/product/{number}, for example /public/product/5905. Or have the signed .jws file ready.

  2. Type it in or upload the file

    Use the checker at the top of this page: the number or the full passport address (also for one item, with ?unit=), or a .jws file of up to 5 MB.

  3. Read the result

    Green means the data is unchanged since xProduct sealed it, with the product, passport, operator and key shown. Red means do not rely on that copy.

Where does a signed file come from?

Anyone can download it from the passport API: the passport and its seal in one file, named passport-{number}.jws. Add ?unit= for one serial-numbered item. Signed-in users find “Download signed passport (.jws)” in the product's passport menu.

GET /api/dpp/{number}/en18223/signed

A link that checks straight away

Add ?p= and the product number to this page's address and the check starts as the page opens. Handy to send to a buyer or an inspector.

xproduct.eu/passport-seal?p=5905

04/What the result means

Valid, not valid, or not checked

For anything but a valid seal the checker's heading reads “The seal is not valid”, with the reason below it. Details such as the product name and the operator appear only for a valid seal, because in a changed copy they cannot be trusted.

  • Valid

    “The seal is valid”

    Means:The data is exactly what xProduct sealed for this passport and has not been changed since. You see the product name, the passport address, the economic operator, the last update, who sealed it and the key.

    What to do:Check that the passport address and the operator are the ones you expected.

  • Not valid

    “The seal does not match the data”

    Means:The passport was changed after it was sealed, or the seal belongs to other data.

    What to do:Do not rely on that copy. Open the live passport, or ask the company for a fresh signed file.

  • Not valid

    “The key ‘…’ is not one of this site's keys.”

    Means:The seal was made with a key this site does not list: a passport from the other xProduct site (UK and EU have separate keys), or a seal not made by xProduct. Earlier keys of this site stay listed, so they do not cause this answer.

    What to do:Try the checker on the other site. If it fails there too, treat the copy as not verified.

  • Not checked

    “This answer came without a seal”

    Means:The passport was read, but the answer had no seal, for example while signing is unavailable. The passport is still given out.

    What to do:Try again later. Until a seal checks, treat the copy as not verified.

  • Not checked

    “No published passport has this number”

    Means:The number is wrong, the passport is not published, or it is on the other xProduct site.

    What to do:Copy the number from the passport address, or try the other site.

  • Not checked

    A problem with the file

    Means:It is not a signed passport file (a JWS has three parts separated by dots), its header cannot be read, it uses another signature method, it is a seal without the passport data, it is larger than 5 MB, or it could not be read.

    What to do:Download the file again from the passport API. A seal from the X-DPP-Signature header has no data in it, so it cannot be uploaded here. Download the one-file .jws instead, or check the header seal with your own software (section 06).

There is no “expired” answer. A seal has no end date. Seals made from 11 November 2026 also show when they were made (“Sealed on”), next to the passport's own “Last updated”. Earlier keys of this site are kept in its key set, so older seals can still be checked; the checker says when a seal was made with an earlier key.

05/What carries a seal

The standard passport answers are sealed

Each sealed answer carries the seal in its X-DPP-Signature header over the exact bytes of that answer, with a link to the public keys. The one-file download holds the passport and the seal together. The seal always covers exactly what that caller received, also for professional access and earlier versions.

Sealed

  • GET /api/dpp/{id}/en18223The passport in the standard format. Add ?unit= for one serial-numbered item.
  • GET /api/dpp/{id}/en18223/signedThe passport and its seal in one compact JWS file (application/jose), to keep and pass on.
  • GET /api/v1/dpps/{passport id}The standard read route, also for one element with /elements/{path}.
  • GET /api/v1/dppsByProductId/{product identifier}The current passport found by a product identifier: a GS1 Digital Link, a GTIN or the passport address.
  • GET /api/v1/dppsByIdAndDate/{passport id}?date=An earlier version of the passport, as it was on that date.

Not sealed

  • The older JSON answers at /api/dpp/{id} and /api/dpp/gtin/{gtin}.
  • The full answer for authorities, the data dictionary, the list of versions and lists of passport ids.
  • Error answers, which are never sealed.
  • An answer given while signing is unavailable: the passport still goes out, without a seal. The one-file download answers “not available” instead and points to the unsealed answer.

06/For developers and auditors

Check it yourself, without our website

The seal is a standard JWS, so any JOSE library or the WebCrypto built into browsers and Node.js can check it. You need the answer, its seal and our public key set.

  1. Read a sealed answer and take the X-DPP-Signature header. It looks like header..signature: nothing between the two dots, because the data is the answer itself (a detached seal, RFC 7515 Appendix F).

  2. Put the body of the answer, exactly the bytes you received and base64url-encoded, between the two dots.

  3. Find the key in /.well-known/jwks.json whose kid matches the seal header, and verify the result as an ES256 JWS. A .jws file already holds the data: verify it as it is.

In the seal header

alg · kid
ES256 and the id of the key that made the seal
iss · jku
The site that sealed it and the address of its key set
sub
The passport address
xp_operator
The economic operator's id, such as its GLN
xp_sealedBy
“platform”: sealed by xProduct for that operator
iat · exp
iat: when the seal was made, in seconds since 1970 (UTC), by xProduct's server clock; not a qualified time stamp, and missing on seals made before 11 November 2026. exp is not used: the seal has no end date
import { webcrypto as c } from 'node:crypto';
const site = 'https://xproduct.co.uk';
const res = await fetch(site + '/api/dpp/5905/en18223');
const body = Buffer.from(await res.arrayBuffer());   // the exact bytes
const [head, , sig] = res.headers.get('x-dpp-signature').split('.');
const { kid } = JSON.parse(Buffer.from(head, 'base64url'));
const { keys } = await (await fetch(site + '/.well-known/jwks.json')).json();
const jwk = keys.find(k => k.kid === kid);
const key = await c.subtle.importKey('jwk', jwk,
  { name: 'ECDSA', namedCurve: 'P-256' }, false, ['verify']);
const ok = await c.subtle.verify({ name: 'ECDSA', hash: 'SHA-256' }, key,
  Buffer.from(sig, 'base64url'),
  Buffer.from(head + '.' + body.toString('base64url')));
console.log(ok ? 'seal valid' : 'seal NOT valid');
Tested on 11 November 2026 against the live UK passport 5905: it prints “seal valid”, and with one byte of the data changed the check fails. For a .jws file, check it as a normal compact JWS.
  • Public keys

    A standard JWK set at /.well-known/jwks.json: EC P-256 keys for signing (ES256). Cached for an hour.

  • One key set per site

    xproduct.co.uk and xproduct.eu each have their own signing key and list only their own public keys.

  • Key changes

    A new key is used soon after it is brought in. Older keys stay in the set while they are still active, newest first; the seal's kid says which one to use.

  • Offline later

    Keep the .jws file and a copy of the key set, and you can check the seal later with no connection. This page itself needs to be online.

Take the public keys from the site itself, not from the seal. Our checker trusts only this site's own key set and ignores the jku address in the seal, so a forged seal cannot point to a key set its maker controls. Do the same in your own software.

07/Seal, ledger and blockchain

Three separate layers, each with its own job

The seal is not on the blockchain. Nothing about a seal is written to the chain. It works next to the product ledger and the blockchain records, and each answers a different question.

  1. 1

    Passport seal

    Is this copy unchanged, and did it come from xProduct?

    A digital signature on each standard passport answer, checked with the public keys. It stays with every copy.

  2. 2

    Product ledger

    What changed, when, and by whom?

    Every change to a product is an entry linked to the one before by its hash, so a gap or an edit shows. The chains are checked every night.

  3. 3

    Blockchain record

    What did the ledger look like on that day?

    Each night, if anything changed, one fingerprint of the account's checked ledgers is recorded on Polygon. Certificate fingerprints are recorded there too; the passport links to the transaction.

08/Privacy

What a check sends, and what it does not

The maths runs in your browser with its built-in WebCrypto. You do not need an account, and the checker keeps no record of what you check.

  • Checking by number

    Your browser reads the public passport and the public key set from this site, as it would when you open the passport. Those reads are ordinary page requests, like opening the passport itself.

  • Checking a file

    The page reads your file through its live connection to our server and hands it straight back to your browser for the check. The file is not saved.

  • No account, no record

    You do not sign in to check a seal, and the checker does not save the result. Close the page and it is gone.

09/FAQ

Short answers

Checking seals in your own system, or a question we have not answered? Write to us.

Does a valid seal mean the product meets the law?

No. It shows that the data is unchanged since xProduct sealed it, for the passport and operator named in it. What the passport says remains the company's own statement.

Is this the manufacturer's own electronic seal?

Not yet. Today xProduct seals the passport as the platform that holds it, on behalf of the economic operator. A seal in the operator's own name, with a certificate recognised in the EU, is a later step that waits on EU rules.

Do seals expire?

A seal has no end date. Earlier keys of this site stay in its key set, marked as earlier keys, so older seals can still be checked here. Anyone who kept a copy of the public key set can also check them offline.

Can I check a seal offline?

Yes, with your own software: keep the .jws file and a copy of the key set from /.well-known/jwks.json, and verify with any JOSE tool. This page needs a connection because it reads the site's keys.

Why does a UK passport fail on the EU site?

xproduct.co.uk and xproduct.eu each seal with their own key, and each checker trusts only its own site's keys. Check a passport on the site it comes from.

Is the seal stored on the blockchain?

No. The seal is a signature that travels with the data. The blockchain holds separate records: a nightly fingerprint of each account's checked ledgers and fingerprints of certificates.

Can I check an answer with professional access?

Those answers are sealed too, but the checker reads passports by number without signing in, so it sees the public answer. To check a professional answer here, download it as one file from /api/dpp/{id}/en18223/signed with your partner token and upload that file, or check the header seal with your own software.

Which standards does the seal follow?

It is a JSON Web Signature (RFC 7515) with ES256 and a standard JWK key set. It is designed to follow EN 18246 clause 4.7 as a first step, and the answers use the EN 18223 format (draft). This is a description, not a statement of conformity.

Is my passport's data hidden by the seal?

No. The seal does not encrypt anything. Public data stays public; restricted data is still shown only to people with access.

A passport seal you can check yourself

Digital product passports are read by buyers, inspectors and other companies' systems, and copies get saved and passed on. xProduct seals the standard passport answers with a digital signature, so anyone can check that a copy is unchanged and came from xProduct, here in the browser or with their own software.

Technical basis: JSON Web Signature (RFC 7515) with ES256 (ECDSA, P-256, SHA-256) and JSON Web Key sets (RFC 7517). The seal is designed to follow EN 18246 clause 4.7 as a first step; the answers use the EN 18223 format (draft) through EN 18222 read routes. This page describes how the seal works; it is not a statement of conformity.

Passports people can check, not just read.

Passports you publish on xProduct are sealed in their standard answers, with nothing for you to set up. Start free, or book a demo and we will show you the passport, the ledger and the seal.