What the service holds, how fresh it is, how often it is right, and who uses it
Two kinds of number. The first block is read live from the same endpoints anyone can call. The second is typed in by hand on the date shown, in the manner of healthchecks.io's about page, because a one-person service earns trust by publishing the numbers it would rather round up.
/stats)Warehouse data as of … (the date of the newest certificate in it; the sync itself runs daily). The research refresh that rebuilds the notes, the answer pages and the JSON below runs weekly.
Read from coverage.json and vendor_customers_profile.json, the same files the notes are built from.
| Measure | Value | Meaning |
|---|---|---|
| Period observed | … | contiguous months in the warehouse; the first and the current month are partial |
| Certificates in the last complete month | … | distinct certificates (one fingerprint counted once, however many of the … log sources carried it) |
| Gold pairs (Wikidata LEI ↔ domain) | … | the set resolution is scored against; skews to large listed companies |
| absent from the OV/EV warehouse | … | coverage, not error: the domain has no organization-validated certificate |
| present, name matches the gold LEI exactly | … | the resolution the product makes |
| present, name matches loosely | … | containment only; note 1 counts it as weaker evidence and never assigns an LEI on it |
| present, LEI missing from this GLEIF snapshot | … | the gold LEI is no longer in the register snapshot the run used; usually a merger or a lapsed registration |
| present, certificate names something else | … | a registered-name disagreement, not an error rate: note 1 decomposes it, and most are the owner's own group or a vendor's certificate on the owner's domain |
| Confirmed vendors | … | vendors whose customers note 3 profiles |
| Customer domains across them | … | domains carrying a confirmed vendor's certificate without its brand |
| resolved to one legal entity | … | the rows that carry an LEI |
Counted from the service's own tables and the verification set on that date. Updated when something changes, with the date moved.
| Measure | Value | Note |
|---|---|---|
| Paying customers | 0 | Pro was priced on 2026-09-07; no Pro key has been issued to anyone but the operator |
| Monthly recurring revenue | $0 | |
| Active API keys | 16 | 14 free, 2 Pro (the operator's own) |
| Queries logged since 2026-03 | 18,786 | from the monthly aggregate; the bulk are the operator's own tests and benchmarks. Unkeyed pages and endpoints are never counted |
| in the last 90 days | 191 from 10 keys | the live log window; older rows are archived (terms, section 6) |
| Human verdicts in the verification set | 177 | 105 yes, 48 no, 24 unsure; one labeler so far |
| Public verification labels | 0 | the public pilot has not started |
| Cost to run | about $5 a month | the Cloudflare Workers Paid plan plus small usage charges and the domain; the batch work runs on the operator's own machine |
Per-key or per-customer detail, query contents, and anything from a source that is not public. The privacy section says what is logged and for how long; the research notes say how each measure is defined and where it fails.