What Third-Party Tested Means

ON THIS PAGE

1. Key findings
2. How many say it
3. When the phrase names nothing at all
4. When the name attached matches on some pages and not others
5. When the phrase means an open, checkable trail
6. What actually separates one use of the phrase from another
7. Limitations and open questions
8. Sources

Three words, printed on a storefront, can mean a laboratory ran a specific test on a specific batch and published the result, or they can mean nothing was checked and nothing is checkable. Nobody issues "third-party tested" the way a standards body issues an accreditation number, and this ledger holds the full range the phrase actually covers.

How many say it

25 of the 126 supplier records in this publication's ledger, read 2026-09-18, contain the string "third-party test" or "third party test" somewhere on the vendor's own pages, a stem match that counts a record whether the page reads tested, testing, or test. That count says only that some form of the words appears. It says nothing about whether a laboratory is named, whether a document is linked, or whether the document that is linked actually comes from whoever the page credits. Those three questions are what separate one use of the phrase from another, and this ledger has a case for each.

When the phrase names nothing at all

Peptide Store's central quality claim, read 2026-08-25, is independent third-party testing with a Certificate of Analysis on every order. That wording is this publication's own summary of what the home, about, category, and RT10 product pages promise between them, not a sentence quoted from any one of them. No laboratory is named anywhere on any of those pages, and no document is linked from any of them either. This publication tried seven guessed certificate-index URLs on the site the same day, the kind of address a vendor with a real COA hub typically uses, and every one returned HTTP 404. The claim is not merely unverified. It supplies no laboratory name, no document, and no path a visitor could follow to check it, which is a different and thinner thing than a claim this publication simply has not yet confirmed.

When the name attached matches on some pages and not others

Alphamino's own About page, read 2026-08-26, is more specific than Peptide Store's claim and, on its face, more checkable: "Third-party testing: Where applicable, batches are verified through Janoshik independent analysis with Certificates of Analysis (COA) linked from the product page for the batch in stock." Naming a specific laboratory is what turns a claim into something a reader could look up. But the certificates carried on Alphamino's own GHK-Cu and MOTS-c product pages, opened the same day, are PeptideVerify documents, not Janoshik ones. The mismatch is real and it is partial: two other product pages, BPC-157 and TB-500, carry Janoshik documents of the kind the About page describes, so which laboratory a buyer finds depends on which product they open rather than on what the About page says. A named laboratory is worth more than no laboratory named at all, and it is still only worth as much as it matches what a buyer finds when they click through.

When the phrase means an open, checkable trail

Genpeptide runs a browsable per-product certificate lookup, read 2026-08-20, structured as a listing rather than a single catalog-wide badge. Its own header states "Every batch is third-party tested by accredited laboratories," and the lookup backs the sentence with entries specific to a batch: a compound and strength, a lot number, and a test date, in the vendor's own format, for example "5-Amino-1MQ 50mg / Batch / Lot GPAMI50051226 / Tested 05/18/2026." Each product also carries a "COA History" listing prior lots rather than showing only the current one. The same three words that name nothing on Peptide Store's pages and mismatch what they name on two of Alphamino's product pages sit, here, in front of a document structure a buyer can open and check without asking anyone.

What actually separates one use of the phrase from another

Three questions sort the cases above without needing to trust any of them: does the page name a specific laboratory, rather than describing testing in general terms; does a linked or downloadable document actually exist, rather than a promise that one is available; and when a document does exist, does it come from the laboratory the page credits, rather than a different name entirely. Peptide Store fails the first two. Alphamino passes the first, and on the third its answer splits by product: the BPC-157 and TB-500 documents come from the laboratory the About page credits, the GHK-Cu and MOTS-c documents come from a different one. Genpeptide passes all three, not because its header sentence is worded any more strongly than the other two, but because a specific, checkable document sits behind it.

Limitations and open questions

This piece describes three dated cases, read between 2026-08-20 and 2026-08-26, and a storefront's claims or the documents behind them can change at any time after those dates. The 25-record count is a substring search over this publication's own ledger, run 2026-09-18, for "third-party test" or "third party test," which counts a record whether its page reads tested, testing, or test; narrowing it to the exact word "tested" returns 12 of the 126 records instead, and a looser search would return more, so the figure describes the search as much as the corpus; it describes what this publication's dossiers recorded, not a market-wide count of every seller using similar language. This piece takes no position on whether Alphamino's PeptideVerify documents are themselves accurate, or on Genpeptide's underlying laboratory relationships beyond what its own lookup page states; it reports what each site shows a visitor who follows the phrase to what backs it.

The words on the page cost a seller nothing to print. What separates one use from another is whether anything opens when a reader tries to check it.

Sources

Supplier observations are this publication's own, from the dossier record in ledger/vendors.json: Genpeptide, read 2026-08-20; Peptide Store, read 2026-08-25; Alphamino, read 2026-08-26. The 25-record count was run directly against ledger/vendors.json on 2026-09-18. Vendors are named here, never linked, per site policy.