VNPEPS
🔍 Investigation · 2026-11-20 · method reproducible

How we checked one peptide seller's certificates — and what the PDF metadata revealed

A forensic breakdown of 16 COAs: all printed from a headless browser within 26 minutes; the 'lab verification' fails the lab's own registry. We name no one — we show the method you can repeat on any document in 5 minutes.

Contents 1. Context: why we checked someone's COAs at all 2. Finding #1: HeadlessChrome metadata ×16 3. Finding #2: the 26-minute production window 4. Finding #3: Janoshik verification — 'test not found' 5. How to repeat our steps 6. What a verifiable approach looks like 7. Interactive checker: test your own COA

1. Context

We are VietPeptide, selling research peptides from Da Nang. Our principle: we do not claim certificates we don't have — instead we teach buyers to verify any document. When a seller appears on the market with perfect 'laboratory' COAs for every product, we did what any buyer should: checked the documents by open methods.

2. Finding #1: HeadlessChrome metadata

Fact · verifiable in 30 seconds

All 16 PDFs carry browser-print metadata

Every PDF carries service metadata: Producer and Creator. Laboratory systems (Waters Empower, Thermo Chromeleon) write their own names there. In all sixteen documents from one seller:

/Producer (Skia/PDF)
/Creator (…HeadlessChrome/149…)

Skia/PDF — Chrome's graphics engine. HeadlessChrome — a screenless browser used for automated page-to-PDF printing. This is not laboratory software — it's a 'made a page → printed to PDF' pipeline.

Verify yourself: download any COA PDF → right-click → Get Info / Properties → check the 'Created with' field.

3. Finding #2: the time window

Fact · verifiable from metadata

16 'independent' certificates created in 26 minutes

File-creation timestamps (from the same metadata):

FileCOA №Created (UTC)
tb-500.pdfCOA-2026-2087Jul 1 2026 05:07:17
slu-pp-332.pdfCOA-2026-2649Jul 1 2026 05:09:23
cjc-ipamorelin.pdfCOA-2026-3168Jul 1 2026 05:11:33
mt-2.pdfCOA-2026-3925Jul 1 2026 05:13:44
selank.pdfCOA-2026-4806Jul 1 2026 05:18:04
… and 9 more files in the same window …

Sixteen 'analyses of different products' created ~2 minutes apart — in one sitting. Laboratories do not analyze 16 different compounds in 26 minutes.

4. Finding #3: verification fails

Fact · verifiable on the lab's official site

A Janoshik-branded certificate is not found in the Janoshik registry

The seller's site publishes a 'TEST REPORT' with: Task #195511, unique key 3TMVHXRXWF52Y, batch GHKCU-260417-A, endotoxin 1.321 EU/Vial.

Janoshik's official public verifier — janoshik.com/verification — responds:

"No test found for the given task number and unique key."

We checked with both 195511 and #195511 — same result. The document presented as 'Janoshik-verified' is not in the Janoshik registry itself.

Verify yourself: open janoshik.com/verification, enter 195511 and 3TMVHXRXWF52Y. Screenshot the result. (Our check date: November 2026.)

5. How to repeat our steps

  1. Download the PDF of any COA from the seller's site (not a screenshot — the PDF file).
  2. Open metadata: macOS — Quick Look + Cmd+I; Windows — file properties; online — pdfinfo or exiftool. Check Producer and Creator fields.
  3. Assess: lab software (Empower, Chromeleon, MassLynx) — plausible. 'Skia/PDF' / 'HeadlessChrome' / 'Chrome' — printed from a browser.
  4. If a lab with a verifier is named (Janoshik etc.) — enter the credentials there. 'Not found' = the lab never confirmed this document.
  5. Check dates: files created in a batch within minutes — red flag.
  6. Ask the seller directly. An honest answer explains the origin. Pressure ('hurry, discount ends') — walk away.

6. What a verifiable approach looks like

✅ Verifiable

  • Seller honestly says: 'COAs are available from the manufacturer on request' — and gives the contact
  • Prices with an update date
  • Written confirmation of composition and total before payment
  • Real product photos (not stock)
  • Direct questions about documents answered with facts

🚩 Red flags

  • 16 perfect PDFs with HeadlessChrome metadata
  • 'Verified by [lab]' — but the lab's registry doesn't know the document
  • Files created in a 26-minute batch
  • 'Only now' discount when asked about documents
  • Chat 'review' screenshots instead of published ones

7. Interactive checker

We packed it all into one tool — the interactive COA checker: run 8 checks on any certificate and get a verdict. Save the result and show it to any seller — including us.

Our answer to the trust question

🇻🇳 We claim no batch COAs. We publish a dated price index, real photos and 19 reviews 5/5 with photos. Vet us just as hard.

People also search