How LaunchLedger checks evidence

A dated observation is useful. A guessed business story is not.

What we check

We fetch robots rules, one public HTTPS homepage and at most one same-site contact or pricing page. We inspect the initial HTML for a title, description, language, mobile viewport, indexing directives and a small set of link failures. We do not execute JavaScript or submit forms.

Blocked access, parked domains and thin HTML produce limited coverage, not a list of missing features. Findings include the page, observation time, why it may matter and a next step to verify. A noindex directive can be intentional.

Discovery is a signal, not proof of launch

Our bounded sample comes directly from Cloudflare’s Nimbus Certificate Transparency log. Certificates renew for established businesses too. Certificate time, our first observation, a provider-reported date and a verified business launch are separate fields. We do not call an unchecked domain a new business.

Chrome’s log policy requires unrestricted retrieval and sharing of log data. Site content has separate access rules. Reports respect robots rules; operator enrichment requires a recorded source review. We do not use registration identities, residential addresses or private profiles.

Public business formations

We also sample five recent company records from the Colorado Department of State’s Public Domain dataset, checking its license and schema each run. We retain only entity ID, name, type, status, formation jurisdiction and date. We exclude officer, registered-agent and address fields. Formation does not establish trading, a website or vendor needs; unmatched records stay unmatched.

What remains unknown

Ownership, formation date, original launch, buying intent, revenue, budget, rendered usability, accessibility conformance, search ranking, security and checkout success are not established by this report. Public contact-page links provide a route to inspect, not consent to marketing.

Limits and corrections

Checks allow at most ten bounded requests and three redirects per page, with public-address validation, response-size limits and timeouts. Reports may be cached for 15 minutes. The free service allows 15 attempts per hour per network address and 250 uncached reports per UTC day.

To correct or remove published evidence, contact RTG Product Labs with the public domain and reason. Do not send credentials or private documents.