A Janoshik test report is only evidence if it is genuine. The document that circulates with a peptide, a screenshot or a PDF, is easy to copy, easy to edit, and easy to attach to the wrong sample. This guide covers how to confirm that a Janoshik certificate is real and unaltered using the laboratory's own public verification tool, what a successful verification actually proves, and the limits of what it can tell you. Every description below reflects the tool as it is published on the company's site; nothing here is a claim about product quality.
Why a report has to be verified, not just read
A certificate of analysis is a file. Files can be altered. A purity figure can be changed in an image editor, an old report can be reissued under a new date, and a genuine report from one batch can be presented alongside an unrelated vial. The World Health Organization treats falsified documentation as part of the wider problem of substandard and falsified medical products, which it defines to include products that deliberately misrepresent their identity, composition, or source. A forwarded report sits in exactly that risk category until it is checked against the issuing laboratory's own records.
This is why verification is a separate step from reading. Knowing how to read a peptide certificate of analysis tells you whether the numbers on the page are internally credible. Verification tells you whether the page itself is the one the laboratory issued. Both are needed, and reading a well-formatted report is not a substitute for confirming it exists.
The Janoshik Verify tool
Janoshik Analytical (registered as Janoshik s.r.o., ICO 17668727, Prague, per the public company registry record) publishes a public verification page reachable from the Verify item in its site menu, at janoshik.com/verify. The page is headed "Verification" and states its purpose plainly: "Here you can verify the authenticity of any test conducted by our company."
The tool is a short form with two inputs:
- Task number. The report's identifier, entered in the format shown by the field placeholder, "Task number (eg. #00000)." The field's own instruction states that the task number "is located on top left of each report."
- Unique key. A second identifier, entered in the "Unique key" field. Its instruction states that the key "is located on the bottom of each report," and adds that "No key necessary for public tests."
Submitting the form (the button is labelled "Verify") returns the record the laboratory holds for that task. Publicly listed tests can be looked up by task number alone, which is why the key is described as optional for them. Non-public reports require both the task number and the unique key printed on the specific document.
The company also states that every report is verifiable "via Verify tab in the menu or QR code on the report." The QR code is a shortcut to the same check: scanning it opens the stored record for that task, so you reach the identical verification result without typing the identifiers. Whether you scan the code or enter the task number and key by hand, the thing being confirmed is the same, that the report exists in the laboratory's database as issued.
Verifying a report step by step
- Find the two identifiers on the report. The task number is at the top left; the unique key is at the bottom of the document.
- Open the Verify page at janoshik.com/verify directly, by typing it into the address bar, rather than following a link embedded in a message from the seller. Reaching the tool independently removes one way a forwarded document could point you at a lookalike page.
- Enter the task number, then the unique key. For a report the lab lists publicly, the task number on its own is enough.
- Submit and compare. Read the record the laboratory returns and compare it field by field against the document in your hand: the task number, the test or sample type, the date, and every measured value. A genuine report matches its stored record exactly.
- Treat any mismatch as a failure. If a value, a date, or the sample description differs from what the tool returns, or if the task number and key do not resolve to a record at all, the document in front of you is not verified and should not be relied on.
What a successful verification proves
A verification that resolves and matches confirms one thing precisely: the report exists in Janoshik's database as issued, and the copy you are holding has not been altered. The values you can read on the PDF are the values the laboratory recorded for that task. In practical terms, it rules out the edited-number, reused-document, and fabricated-certificate problems that a report is exposed to the moment it leaves the laboratory.
That is a meaningful result. Most disputes over a circulating certificate are settled at this step, because a forged or edited document either fails to resolve or returns figures that do not match the image being passed around.
What verification does not prove
Verification confirms the document. It does not, on its own, confirm the vial. The distinction is the core of careful sourcing.
- A verified report describes the specific sample that was submitted, not necessarily the unit in your hand. The result transfers to your product only if the batch or lot identifiers on your vial match the batch or lot on the verified report. A genuine, verifiable certificate attached to a different batch tells you the laboratory did honest work on some sample; it does not tell you about yours.
- Verifying a public test confirms the lab published that result for a submitted sample. It says nothing about who submitted the sample or where a product was later sold. The report is a data point about one submission, not a chain of custody for a purchase.
- A verified value is still method- and sample-specific. Purity reported as HPLC area-percent reflects what the chosen detector and wavelength can see, and an identity confirmation and a purity figure answer different questions. Verification does not change what the underlying measurement did or did not cover; for that, read the report on its own terms.
- Redaction of the supplier's identity does not invalidate a verified report. A vendor that removes its own or its manufacturer's name from an otherwise complete, batch-matched, independently verifiable certificate is following a normal commercial-privacy practice. What the analytical data means does not depend on who sold the product. Trust rests on three things you can examine directly: the batch on the vial matching the batch on the report, the methods the report states it used, and the report being verifiable at its source. Identity of the seller is not one of them.
The complete specification a report should contain, so that its fields can be matched to a batch in the first place, is formalised in the International Council for Harmonisation's Q6B guideline on specifications for biological products. A report you can verify but cannot tie to a batch number is genuine and still incomplete for your purposes.
The bottom line
Verifying a Janoshik report takes two identifiers and one lookup: the task number from the top left, the unique key from the bottom, entered at janoshik.com/verify. A match proves the report is real and unaltered. It does not prove the material in your vial is the material that was tested, which is a separate question answered only by matching batch numbers and reading the methods behind the result. For the wider context of who Janoshik is and how its reports are structured, see Janoshik Analytical: independent peptide testing explained, and for the difference between a report you can check and a vague "COA on request" promise, see third-party tested versus COA on request, decoded.