Verify a report
Scan the QR code on the certificate, or type the report number and verification key below. The record returns the sample description, the result of every determination with the method it was run under, the date of issue and the current status. It never discloses the client.
There is no browsable list of certificates and there will not be one. A public register would disclose who tested what and how often. A record resolves only for someone holding the certificate, which is exactly the person entitled to check it.
| Report number format | AN-YYYY-NNNNN |
| Verification key | 10 characters |
| On the certificate | QR code and printed key |
| Public list of certificates | None, by design |
| Register retention | 10 years |
| Manual check | lab@analyton.com |
The key is the access control
The report number alone resolves nothing. The number and key together form the address of the record, and the QR code on the certificate is that address. That is why there is no search and no list: a record cannot be found by guessing, only by holding the paper.
The key uses an alphabet without I, L, O, U, 0 or 1, so a key copied by hand from a printed certificate cannot fail on a confusion between a zero and an O. Case does not matter.
No certificates have been issued yet, so no record will resolve today. The mechanism is live and a certificate issued tomorrow is verifiable the moment it exists.
Verification confirms that a certificate with that number and key was issued by ANALYTON, for the sample described on it, on the date shown, and that it is current rather than withdrawn. That is a real and useful fact, and it is the whole of it.
It does not re-run the analysis. It does not confirm that the vial in front of you is the vial that was tested, because nothing on a piece of paper can establish that. A certificate travels more easily than the material it describes, and the commonest misuse in this market is a genuine certificate attached to a different batch.
The defence against that is batch-level testing rather than certificate-level trust: a result on the batch you are buying, not a result on a batch someone once bought. That is what the variance option on the price list exists for.
| Report number | Confirmed or not found |
| Date of issue | Yes |
| Sample description | Yes |
| Determinations performed | Yes, and any ordered and not performed |
| Status | Current, withdrawn or superseded |
| Client identity | Never disclosed |
| Reported results | Every determination, with its method |
| Peptide delivered | In milligrams, against the label |
| File fingerprint | SHA-256 of the issued file |
| Machine readable | JSON on the same path |
Why certificates are withdrawn rather than corrected
A certificate found to contain an error is withdrawn and replaced by a new certificate with a new number, which references the one it supersedes. The withdrawn number stays in the register, marked withdrawn.
The alternative, amending a certificate in place, means a document can change after it has been read, quoted and relied on. A reader who saved a copy would hold something that no longer matches the record and would have no way of knowing. Withdrawal is noisier and it is the only version that leaves an audit trail.
How do I check that an ANALYTON certificate is genuine?
Scan the QR code printed on it, or enter the report number and the verification key into the form on this page. The record returns the sample description, the result of every determination with the method behind it, the date of issue and whether the certificate is current, withdrawn or superseded. The client is never disclosed.
Can I check that my copy of the certificate has not been altered?
Yes. The record carries the SHA-256 of the certificate file exactly as it was issued, and the command to check a copy against it. If the two strings match, the file is byte for byte the one this laboratory issued. A document cannot carry its own fingerprint, which is why it is held in the register rather than printed on the paper.
What does verification actually prove?
That a certificate with that number and key was issued by ANALYTON, for the sample described, on the date shown, carrying the results the record shows, and that it has not been withdrawn. Where a certificate in circulation differs from the record, the record governs. It does not re-run the analysis and it does not prove that the material in front of you is the material that was tested.
Why can a certificate be shown as withdrawn?
Because certificates found to contain an error are withdrawn and superseded by a corrected certificate carrying a new number, rather than amended in place. The withdrawn number stays in the register marked withdrawn, with a pointer to the certificate that replaced it.
Is there a public list of ANALYTON certificates?
No, and there will not be. A browsable register would disclose who tested what and how often, which is the client's business. A record is reachable only by holding the certificate: the QR code carries the report number and its verification key, and without the key the record does not resolve.
Can a certificate be verified by someone who is not the client?
Yes, and that is the point. A buyer holding a certificate and its key can confirm it exists and has not been withdrawn, without needing anything from the seller. Verification returns the sample description and every reported result; it does not disclose the client.
Updated 2026-09-01