For each signal: what it is, how we determine it, and how you can verify it yourself. Every one is drawn from a source you can open.
Operating entity
What it is The legal entity (usually an LLC) that runs the storefront — the strongest positive identity signal we hold.
How we determine it We resolve it by one of five methods, and we always label which one:
- StrongState registry recordan active Secretary-of-State business filing
- StrongUSPTO trademark registrantthe owner of a live federal trademark in a peptide-relevant class
- SupportPublic federal recordan entity named in another public federal filing
- SupportUSPTO trademark applicanta pending (not yet registered) trademark application
- Self-assertedSelf-disclosedan entity the vendor names on its own site, not yet independently confirmed
Verify it yourself Open the state Secretary-of-State business search or the USPTO TSDR record linked on the profile and search the entity name. A trademark or SoS record is a sworn public filing; a self-disclosed name is the vendor’s own claim until a registry confirms it.
Domain age
What it is How long the storefront’s domain has been registered. 6 months is the floor for Verified; 5 years counts as an established presence on its own.
How we determine it We read the domain’s creation date from RDAP (with a WHOIS fallback) at the authoritative registry.
Verify it yourself The profile’s Verify link opens a public WHOIS/RDAP lookup for the domain; the creation date we cite is on that record. A newer domain is a neutral factor — it lowers confidence, not trust.
SSL / TLS certificate
What it is The certificate the site serves over HTTPS, and what kind of validation stands behind it.
How we determine it From a live handshake, cross-checked against certificate-transparency logs. An organization-validated (OV/EV) certificate carries a CA-verified legal organization — a factual positive. A domain-validated (DV) certificate (e.g. Let’s Encrypt) is the neutral norm for most sites. A certificate that does not validate (expired, self-signed, or host-mismatched) blocks Verified — stated as a neutral technical fact, not an accusation.
Verify it yourself The Verify link opens crt.sh for the domain, where you can inspect every certificate ever issued for it.
Ownership transparency
What it is Whether the domain’s registrant is disclosed or hidden behind a WHOIS privacy/proxy service.
How we determine it From the registrant fields in the RDAP/WHOIS record. A named registrant organization is a mild transparency positive. Concealment behind a privacy service is near-universal and neutral — it lowers confidence, never trust, and never moves the tier.
Verify it yourself The Verify link opens an RDAP lookup; you can read the registrant (or the privacy-service name) directly.
Location check
What it is A plain notice shown when the country on the domain’s registration differs from the country the store itself states (the address on its own contact or about page, or its registered operating company).
How we determine it We compare countries only, and only when both facts are known with a source and a date. The registration country is re-read from the public RDAP record every night. A registration hidden behind a privacy service never triggers it, because the address shown is the service’s, not the store’s. It is a notice, not a rating — it never changes the tier and never adds Caution.
Verify it yourself The notice links both sources with the date each was checked. Stores can correct either fact through the correction form.
Registration jurisdiction
What it is Whether the operating entity is formed in a privacy-forward state whose filings limit public disclosure of owners and officers.
How we determine it From the registration state on the resolved entity. This is a neutral registration-jurisdiction note — a common, lawful choice, presented as context, never a negative finding.
Verify it yourself The state named on the profile is the entity’s own filing jurisdiction; the SoS search for that state shows what its records do and don’t disclose.
Enforcement & regulatory record
What it is Any public enforcement action on record — FDA warning letter, FTC or ITC action, Health Canada alert, or DOJ criminal case. This is the one signal that is a genuine negative.
How we determine it We screen public agency records. A hit sets the Caution overlay and blocks Verified; a criminal case caps the vendor at the Neutral floor. A clean screen is a mild reassurance; an unscreened vendor simply has lower confidence.
Verify it yourself Each action carries the agency’s reference, date, jurisdiction and a link to the agency’s own record. Open it; the record speaks for itself.
Payment recourse
What it is Whether a purchase carries a chargeback or dispute path.
How we determine it From the payment methods the storefront publicly displays, with one evidence rule (methodology 1.5.1): card acceptance counts only when it is visible at checkout level — a wired-in card processor, the payment icons a Shopify checkout has enabled, or a card option or field at checkout. A card mention in FAQ or footer text alone is recorded as claimed: neutral, never a positive. Where the checkout we could see offers no card and no recourse-bearing wallet, the store is treated as accepting crypto, bank or peer-to-peer only, even if its text mentions cards. A shop that accepts only cryptocurrency or peer-to-peer apps — no cards, no recourse-bearing wallet — leaves a buyer no dispute path. That factual limitation blocks Verified; it is stated neutrally and is not an accusation.
Verify it yourself Add a product to the cart on the vendor’s own site and read the payment options its checkout page offers. Each signal on the profile carries the date we last read it.
Price transparency
What it is Whether the vendor publishes prices we can index and normalise to a single $/mg figure.
How we determine it We index publicly listed prices nightly, ex-shipping, and normalise them to USD per milligram so they compare across pack sizes and vendors.
Verify it yourself Every priced compound on a profile links to the live price view, and the vendor’s own listing is one click away.
Shared identifiers
What it is A notice on a profile when another store in our index carries the same identifier: the same analytics or ad-tracking ID, one security certificate covering both sites, the same phone number, the same street address including the suite number, or the same lab-test batch number or file. Shared identifiers can mean shared ownership, a shared contractor, or a shared service. This is not a finding that the stores are run by the same people, and it never changes a trust tier.
How we determine it Every night we read each store’s home and contact pages (robots.txt respected, with our named crawler) and the certificate its site serves, and compare exact values. Weak overlaps — the same web host, theme, registrar or registered-agent mailing address — never count, and IDs that belong to a shared platform are ignored. A page we could not read never adds or removes a notice. A store’s owner can dispute a notice from their signed-in PeptideIQ account; while that dispute is reviewed, the notice is withheld. Anyone can also report an error through the profile’s correction form — a person reviews it, and the notice stays up meanwhile.
Verify it yourself Each notice names the other store, what matches, and when we first and last saw it. The IDs are in each site’s own public page source; the certificate is in your browser’s padlock view.