- Verification needs two fields: the task number and the unique key. Entering one without the other fails every time.
- Most failures are transcription — the key is case-sensitive and contains characters that are easy to misread from an image.
- A report that genuinely will not verify is not evidence of a mistake. It is the outcome the verification system exists to produce.
- Verify before you buy, not after. A seller who cannot produce a verifying report for the batch you are being sold has answered the question.
The point of a verification key is that it moves the proof off the seller's website. Anyone can publish a PDF. Only the laboratory can confirm that the PDF describes a test they actually ran.
So when a key does not verify, it matters. Before concluding anything, work through the ordinary explanations — most failures are mechanical.
The reports discussed here cover material supplied for laboratory research use only. What a verification confirms is that a named laboratory ran a named test, and nothing beyond that.
Check the two fields
Verification needs both the task number and the unique key. They are different things and they sit in different places on the report.
The task number is short and numeric, near the top — something like #216992. The unique key is longer, alphanumeric and printed at the very bottom, under the line inviting you to verify. Entering one without the other, or entering the batch number in place of either, fails every time.
Many reports also carry a QR code that encodes both. If you are reading the report on a screen, that removes the transcription problem entirely.
Most failures are the key, not the report
The key is case-sensitive and the character set is unkind. In most typefaces a capital I, a lowercase l and a digit 1 are close to identical, as are a capital O and a zero, and an S and a 5 at low resolution.
That matters because of how these documents usually reach you. A key copied from a PDF is reliable. A key read off a screenshot, a photograph of a printed sheet, or an image that has been compressed and re-shared a few times is exactly where these errors come from.
Before anything else: get the original PDF, copy the key rather than retyping it, and try again. Also check you have not picked up a trailing space, which is the single most common cause of a key that looks correct and does not work.
If the site itself is down
The verification service is a website and websites have outages. If the page will not load at all, or returns an error rather than a "not found" result, that is an availability problem rather than a verdict on your report. Wait and try again.
A slow or failing lookup is different from a lookup that completes and tells you nothing matches. The second one is a result.
When it genuinely does not verify
If you have the original PDF, both fields entered correctly, and the service is up — and the lookup completes and finds nothing — then you have learned something real.
There are two honest readings, and neither is good for whoever supplied the document:
- The report was never issued. Fabricated certificates exist in this market, and the format is easy to copy. A well-made forgery reproduces the layout exactly and substitutes a key that leads nowhere, which is precisely why layout is not a check and lookup is.
- The report is real but is not for your material. Documents get lifted from one vendor's site and republished by another. The test happened. It was somebody else's.
A related pattern is worth naming: a report displayed with the client name, manufacturer, task number or key blanked out. There is no good reason to redact those fields. Removing them removes exactly the parts that make the document checkable, and the common reading in this market is that the seller is showing you a test they did not commission.
Our article on spotting a fake Janoshik report goes through the forgery patterns in more detail, and what a Janoshik report actually proves covers what a verified one does and does not establish.
Verify before you order
The useful time to do this is before money changes hands.
Ask for the report covering the batch you are being sold, verify the key yourself, and check that the batch number on the report matches the batch you will receive. A seller who can do that has settled the question in about a minute. A seller who cannot has also settled it.
Every batch we sell carries its own report with the task number and key intact, and they are listed on our verification page. If one of ours does not verify, tell us — and believe the laboratory's page over ours.
Sources
Questions this article answers
Why won't my Janoshik key verify?
Most often it is transcription. The key is case-sensitive and contains characters that are easy to misread from a screenshot — capital I against lowercase l against the digit 1, capital O against zero. Copy the key from the original PDF rather than retyping it, and check for a trailing space.
What do I need to verify a report?
Two fields: the task number, which is short and numeric near the top of the report, and the unique key, which is longer and printed at the bottom. Both are required. Many reports also carry a QR code encoding both, which avoids typing either.
What does it mean if a report genuinely won't verify?
Either the report was never issued by the laboratory, or it is a real report for somebody else's material. Both readings reflect badly on whoever supplied it. A completed lookup that finds nothing is a result, not an error.
Why do some vendors black out the task number and key?
There is no good reason to. Those are the fields that make a report checkable, and removing them removes the only thing that distinguishes an independent test from a picture of one. The common reading in this market is that the seller did not commission the test.
Want the certificate for a real batch?
Name a compound and we'll send the manufacturer's HPLC-MS certificate for the batch you would receive — before you order, no account needed.