← All testing lab reviews

Testing laboratory · Reviewed 2026-09-03

TrustPointe Analytics LLC review

Operational read
Young operating lab; not accredited
Operating history
Founded in November 2023
Accreditation
No accreditation confirmed

Legitimacy review

Is TrustPointe Analytics LLC legit?

TrustPointe has solid evidence of genuine service delivery for a young lab. Its lack of accreditation and relatively short operating history should remain visible, while repeat-sample evidence is useful but not universal validation.

Operating identity

The official history says Ashlee Lust founded TrustPointe Analytics LLC in November 2023. The lab lists 1743 142nd Ave, Suite 4, Dorr, Michigan; reports also name Joshua Lust as managing director.

Operating history and strongest evidence

Named founder and director, physical address, transparent storefront, public verifier, and independent completed-sample evidence.

Accreditation scope

No ISO/IEC 17025 or other laboratory accreditation certificate and scope was located.

Methods and intake

The site publishes peptide and blend testing prices, safety panels, metals, and Karl Fischer services with a stated three-to-five-business-day turnaround, though reviewed listings were marked sold out.

Public service record

PeptideCritic's same-sample comparison documents completed TrustPointe work and close within-lab duplicate results. That is useful operational evidence, not a universal proficiency finding.

Important limits

The lab is young, not formally accredited, and current storefront availability is unclear. A small repeatability example cannot establish accuracy across all methods, analytes, and dates.

COA verification

Can I check a TrustPointe Analytics LLC COA?

Enter the verification key printed on the PDF report into the public COA Verification field.

Official destination
Public portal search form
What you need
Verification key
Exact-link rule
No record permalink is exposed. Link to the public LIMS page and show the sanitized certificate key as a copyable field; never include client login credentials.
Stored identifiers complete?
Yes
Record-specific links?
No
Identifier copyable?
Yes

Identifiers on the certificate

  • Verification keyPrinted on the PDF report in its verification section.

Result handling

How each verification state is reported

Exact match

Verify only when the submitted key returns the expected TrustPointe report and matching certificate identity.

No match

An explicit official no-record response is unresolved evidence, not proof that the certificate is invalid.

Conflict

Quarantine the record when the identifier resolves to materially different issuer metadata; do not promote it.

Portal unavailable

Treat a CAPTCHA, login, timeout, outage, private record, or other portal failure as unknown.

Unsupported lab

Retain the certificate as document-only evidence and use the issuer contact route without claiming verification.

Unresolved

Keep the record unresolved until an exact issuer result or documented issuer confirmation is available.

Certificate structure

Multi-page and multi-panel reports

Multi-page

Preserve both pages when present; one of three retained certificates is multi-page.

Multi-panel

Keep each report scope explicit. Do not infer purity or identity from a sterility-only result.

Evidence boundaries

What the record does—and does not—connect

Certificate identity
The retained file, fingerprint, and printed fields identify the certificate artifact.
Issuer verification
An exact issuer lookup confirms an issuer record for that certificate; it does not expand the reported scope.
Tested sample
The findings apply only to the sample described on the certificate.
Product matching
The seller product, strength, and lot must be matched to the tested sample separately.
Physical-vial custody
Neither the certificate nor its portal proves custody of the physical vial a buyer receives.

Review receipts

Records and discrepancies checked

Representative records

  • coa:1adb17d8264e24f81f20c082Orbitrex Acetic Acid Solution lot ACE1125; exact verification-key match for a sterility report.
  • coa:93064b3dd613865a3ae09ca1Orbitrex 1G-SGT 20mg lot SM2010625, report SPL-1962-S01; exact verification-key match.

Concrete discrepancies

  • All three records store the needed verification key, but every displayed destination is the generic LIMS form rather than a specific record.
  • Only two of three records also retain a report ID; the verification key, not the report ID, is the required public input.

Sources

Evidence used for this review

  1. TrustPointe Analyticsofficial
  2. TrustPointe LIMS COA verificationofficial_portal
  3. TrustPointe aboutofficial
  4. TrustPointe peptide testingofficial_method

Reusable integration rule: Store the printed verification key independently from report ID, post it only to the official public form, and keep login failures separate from verification outcomes.

Check the document

Apply this review to a specific certificate

Open the COA checker