01
Identity
A qualitative ID section compares the UV/Vis absorbance maximum against the molecule reference standard listed for the report.
Method Lambda max
Typical result language: match or no match. 
Analytical reports, digitally signed.
Purity Analytics prepares signed Certificate of Analysis PDFs for tests handled through the Purity Analytics workflow, with report metadata checked before delivery.
Certificate of Analysis PA test result
UV-Vis scan 200-400 nm
Identity lambda-max reference comparison
Purity correlation reported percent
Assay Beer-Lambert mg or IU amount
Metals total quantity ppb screen
TAMC compendial aerobic count
TYMC compendial yeast and mold
Digitally signed Signature metadata travels with the PDF file.
Testing intake product and batch metadata
Common report sections identity, purity, assay, metals, TAMC, TYMC
Signed PA COA certificate and integrity metadata
Report sections
Six test sections, described without extra claims.
The COA examples reviewed for this site use UV/Vis report language for identity, purity, and assay rows, then list heavy metals, TAMC, and TYMC rows. This section describes what each row means on a Purity Analytics COA.
Method family named on reviewed COAs UV/Vis spectrophotometry
02
Purity
A purity section reports a full-spectrum correlation against a reference standard and expresses the result as a percent value.
Method Correlation coefficient
Single-component workflows should state their acceptance threshold. 03
Quantitative assay
A quantitative assay uses absorbance, reference concentration, and sample concentration terms to report amount per vial.
Method Beer-Lambert
Reports may show mg/vial or IU, depending on product. 04
Heavy metals
A heavy-metals row reports total trace quantity against a parts-per-billion limit for metals named on the COA.
Method Total quantity
A useful report states the target element list. 05
TAMC
Total Aerobic Microbial Count is a microbial-count section run under defined media, dilution, and incubation conditions.
Method Compendial count
Reported as CFU or CFU/ml against the COA limit. 06
TYMC
Total Yeast and Mold Count is a yeast-and-mold section run under defined media, dilution, and incubation conditions.
Method Compendial count
Reported as CFU or CFU/ml against the COA limit. Blend products
Reviewed blend COAs list per-component quantitative assay rows, then continue with heavy metals, TAMC, and TYMC. Each named component should carry its own stated assay basis and acceptance rule.
- Per component
- quantitative assay
- Shared rows
- metals, TAMC, TYMC
Science library
Read the full method explainers.
The library expands each peptide test into a deeper article: what the method measures, how it works, what a result can support, and what it cannot claim.
Workflow
From PA test request to a customer-verifiable signed COA.
Testing-centered, end-to-end. Purity Analytics only signs COAs after the performing lab certifies the submitted result data; the PDF names the lab and carries research-use-only limitations; digital signing follows report preparation, every signed PDF lands in immutable storage, and the customer can independently verify the signature themselves — no proprietary tools, no trust in our infrastructure required.
Receive test request
Purity Analytics receives the product, batch, and requested report details for testing through its own workflow.
Lab certifies result data
The authenticated performing-lab user certifies that the submitted result data are accurate and that the Purity Analytics COA represents the reported test results. Certification does not turn research-use-only analytical information into safety, clinical, therapeutic, or regulatory approval.
Sign with Sectigo + TSA
After lab certification, the prepared COA PDF is signed in-house with a Sectigo Document Signing certificate using a FIPS-certified USB hardware token (PKCS#11). An RFC 3161 trusted timestamp from timestamp.sectigo.com is embedded in the signature so the moment of signing is provable. The cert chain validates automatically in Adobe Reader through the Adobe Approved Trust List (AATL).
Deliver signed COA
The signed PDF lands in immutable Azure storage at a fingerprinted path, a signed_coa_pdf row records the SHA-256, cert thumbprints, and TSA token, and the QR code on the report routes to a public verification page.
Customer verifies
Anyone scanning the QR code lands on verify.purityanalytics.com — the page re-hashes the linked PDF on every request (Tier-1 hash binding) and shows full cryptographic receipts. Opening the same PDF in Adobe Reader shows a blue "Signed and all signatures are valid" banner; both surfaces reach the same verdict independently.
Signed COAs, explained
Three properties that make a valid COA real.
Every valid COA we issue carries a lab certification record and an independently verifiable PDF signature. The PDF also carries the performing-lab page and research-use-only limitations. Adobe Acrobat Reader verifies the cryptographic seal; the public verify website shows both validation checks and re-hashes the PDF on every request.
Performing lab approval before valid status
Before a COA can show as valid, the authenticated lab user must certify that the submitted result data are accurate and that the Purity Analytics COA represents the reported test results. The PDF names the performing lab, address, website, and certification boundary while preserving the private identity of the certifying person.
Sectigo Document Signing certificate
Every Purity Analytics COA is signed in-house with a Sectigo-issued certificate stored on a FIPS-certified USB hardware token. The private key never leaves the token and is PIN-gated. The signature uses RSA-SHA512 and is timestamped by Sectigo's RFC 3161 trusted timestamp authority.
Validated by Adobe out of the box
The signing cert chains to a root in the Adobe Approved Trust List (AATL), which Adobe Acrobat Reader ships with. Opening a signed COA in Reader produces a blue "Signed and all signatures are valid" banner with zero configuration. The same standards-based PKCS#7 envelope (ISO 32000-2, RFC 5652) is what every PDF tool with signature support reads.
Read the full deep-dive
Lab certification, the performing-lab page, the five-stage signing pipeline, the chain of trust from your COA to the AATL root, the per-request Tier-1 hash binding, and how to verify the signature offline yourself.
Document layer
A signed COA is still a COA first.
The website copy mirrors the current workflow: Purity Analytics handles the test workflow, prepares the COA, checks report metadata, and applies a digital signature layer to the PDF. The test rows describe the report content without adding clinical, health, or performance claims.
PDF digital signature
The signature is document metadata plus cryptographic validation data. It does not replace the analytical method rows, specifications, or measured values printed on the COA.
Test report stays visible
The analytical report content remains the basis of the final package. The signature layer is applied after the Purity Analytics COA is prepared for delivery.
Signature metadata is embedded
A PDF digital signature records signer certificate metadata and lets compatible PDF viewers report whether signed bytes changed after signing.
Report methods stay explicit
The COA rows identify the method language used for each section, such as lambda max, correlation coefficient, Beer-Lambert, total quantity, or compendial count.
Talk to us
Request Purity Analytics testing and a signed COA.
Tell us what products need testing, expected batch volume, and the COA format you need for results produced through the Purity Analytics workflow.
tests@purityanalytics.com Helpful context
- Product categories and expected monthly batch volume
- COA template requirements for Purity Analytics test results
- Whether you need testing intake, COA preparation, or signature handling for PA-produced results