Verify a Certificate

LBX issues two public records. Use this page so you do not mix them up. Award certificates from a regional showcase or the Global Final are stored in the season registry — look them up below. Digitally signed files printed with a QR code that opens cert/verify.html carry a checksum; those are checked on the cryptographic verifier, not in the registry form.

Open signed-certificate verifier Certificate FAQ

1 · Season award (registry)

Printed ID under the name, format LBX-{year}-{track}-{hub}-{serial}. Enter it here. Sample IDs are listed at the bottom of this page. This is the usual path for families, schools and employers.

2 · Signed file (checksum)

If the QR code or URL contains cert/verify.html? and a v= parameter, do not type that ID into the box below. Open cert/verify.html and paste the full URL. The verifier checks the signature in the browser.

The ID is printed under the recipient’s name. Format: LBX-{year}-{track}-{hub}-{serial}.

How the registry works

Each award is written into the registry when the panel signs it. The registry stores category, division, hub, date and the citation. The paper certificate is a picture of that entry, not the entry itself. If a certificate is later revoked — for example after an integrity review — the registry says so, and a scan of the original QR still returns revoked. That is intentional.

How the signed verifier works

Some files are issued with a checksum so they can be checked even if someone only has the URL. That tool lives at https://www.lbx.org/cert/verify.html. It is bilingual. It is not a second registry; it is a check of the parameters on the URL. Staff issuing pages (cert/issue.html and certificate/generate.html) are not public.

If verification fails

A “not found” result usually means a typo, or a delay of up to 48 hours after a showcase. Write to verify@lbx.org with the ID, a photograph, and the recipient’s name. We reply within two working days.

Sample registry IDs

Why two doors

Paper awards need a list. Signed files need a checksum. Merging those into one box would make both weaker: a registry lookup would start failing on URLs, and a checksum tool would start pretending to be a database. If you are unsure which door you want, look at the URL on the certificate. If it contains cert/verify.html, use that page. If it contains a short ID like LBX-2026-AI-NY-0142 and no v= parameter, use the form on this page.