Check a COA in Under Two Minutes
ON THIS PAGE
Key findings
- A COA is only as good as its issuing lab, and the major independent labs operate public portals where anyone can check a report number.
- A certificate that cannot be matched to a record at the lab that supposedly produced it is not evidence of anything.
- Verification takes under two minutes per document and catches the two most common forgeries: edited numbers and invented labs.
- A vendor who links a verifiable report is making a different kind of claim than one who posts a JPEG.
The advice to "check the COA" appears everywhere and usually stops there, as though reading a PDF were the check. It is not. The document a vendor posts is a claim about what a laboratory found, and the check is whether the laboratory agrees. The independent labs that dominate testing in this market publish their reports in searchable databases precisely so that anyone can do this, and it is the step most advice about certificates leaves out.
What follows is the verification route for the testing operations that come up most often in vendor documentation and community guides, as their own sites describe it. Each was checked on 2026-08-20. Portals change; if a step below no longer matches what you see, the lab's current instructions win.
Janoshik Analytical
Community documentation of testing in this market describes the Czech lab as its most widely used independent tester, so its reports are the ones a buyer is likely to meet first. Its reports carry a task number and a unique key, and the lab publishes reports at public.janoshik.com, where entering both returns the lab's own copy of the report. The key is case sensitive. Compare the compound, the batch, the date, and the numbers against the vendor's copy. A mismatch in any of them means the document was altered after it left the lab, and that finding matters more than anything the certificate itself says.
CheckPeptide / Ethos Analytics
CheckPeptide reports carry a unique COA ID, and the operation states that anyone can look one up at its verification page. Its published materials credit Ethos Analytics and describe the lab as ISO/IEC 17025 accredited and FDA registered. Accreditation claims of this kind are themselves checkable: ISO/IEC 17025 accreditation is issued by named accreditation bodies that maintain public directories, and a lab that claims the credential without appearing in one is making a claim you could not verify, which in this market is the same as a warning.
Freedom Diagnostics
Freedom Diagnostics maintains a publicly searchable report database, and its stated position is the one this publication holds too: a report that cannot be looked up independently is marketing. Enter the report identifier from the certificate and compare what returns.
The general procedure, for any lab
- Find the lab's name on the certificate. No lab name ends the check: the document is unverifiable by design, which is a finding.
- Reach the lab's site by searching its name directly, never by clicking a link on the vendor's page. A forged certificate can link to a forged portal.
- Use the lab's own lookup with the report identifier printed on the certificate.
- Compare compound, batch or lot number, analysis date, method, and every figure. The comparison is the verification; retrieving the record proves nothing if you do not read it against the vendor's copy.
- Where a lab has no public portal, its published inquiry address does the same job more slowly. A working analytical lab answers questions about report numbers it issued.
What verification cannot tell you
A verified certificate proves that the lab tested a sample and reported those numbers. It does not prove the sample came from the batch you would receive, or that every vial in the batch matches the one tested. Those are sampling questions, and no portal answers them. Verification removes the forgery risk, which is the cheapest risk to remove, and leaves the ones that only a supplier's consistency over time can address. That consistency is what the ledger exists to record.
Sources: the verification flows above are as described by each operation's own published pages, retrieved 2026-08-20. Community documentation of the Janoshik lookup flow corroborates the task-number-plus-key procedure.
Email updates
New articles and news by email, at most once a day or once a week, whichever you pick.
Respond to this analysis
Corrections, contradictions, and anything you have seen yourself. Responses are read and checked. Verified ones become entries in the ledger or corrections to this page. Nothing posts unverified, and no response is published with anything but the handle you type, or the display name of the account you sign in with. Reporting an error, or asking for this article to come down? Use the Report form below.
Report an error or request a takedown
Reports go to the site's administrators. Nothing is removed automatically.