Verify a certificate
How a third party — customer, auditor, authority — verifies a deliverable, without an account.
By its number
GET https://<space>/livrable/verifier?no=<number> or the form on the qatrax.dev home page: the fingerprint is recomputed and the signature verified.
By the piece itself
The third party sends the sealed JSON it holds: POST /livrable/verifier (body: the JSON from /livrable/telecharger). The response says whether the fingerprint holds, whether the signature is that of the issuing space, and whether the piece is identical to the recorded original.
By the certificate PDF
On qatrax.dev/verifier, upload the certificate PDF: every signature is checked — integrity, signer certificate, declared date and the date attested by the timestamping authority. The file is not kept.
By a detached signature (XML)
As in the EU Official Journal, whose PDFs carry no signature: an XAdES XML file alongside covers them by their fingerprints. On qatrax.dev/verifier, upload that XML and, if you wish, the documents: the page tells whether the signature is valid, who applied it, when, and whether each document is covered. A deliverable’s sealed bundle (/livrable/dossier) is checked this way, or with any XAdES tool.
After a space is erased
A cancelled space is erased, but its certificates remain verifiable: qatrax.dev keeps a public register (numbers, fingerprints, signatures, public key — never the content). The space's verification address redirects to https://qatrax.dev/livrable/verifier. See Cancellation and return of data.
Offline
The fingerprint is the SHA-256 of the livrable field in canonical JSON; the signature is verified with the space's public key (GET /cle-publique, Ed25519).