A website is the supplier's own account of itself, written to persuade. That does not make it useless: it is the easiest place to find claims you can then test elsewhere. This guide is a short routine for extracting those claims, noting what the page structure suggests, and handing the testable parts to a second source.
Read the site as a list of statements: who they are, what they make, where, for whom, with what proof. Copy each statement that your decision relies on onto a sheet, then put a second source next to it. A site that gives you little to copy is also a finding.
Spend time on the pages that commit the company to something: about, quality, certificates, contact and terms.
Company name, legal form and registered address in a footer or terms page. Absence is a question, not a verdict.
Narrow range with process language may point to production; broad unrelated range may point to resale.
Named certificates with numbers, named customers or case notes, as against general adjectives.
A real address, a named department, a domain-matched email versus only a form or a free mail address.
Changes of language quality or terminology between pages may indicate reused content.
Photographs and descriptions cannot be confirmed from a desk.
Pages may be undated and may stay up after a claim stops being true.
Shared templates and sites may point to links between companies or may be ordinary practice.
LATYNEX's verification report compares site statements with public records and other sources, citing each, and marks what could not be checked.
Match the name and legal form on the site with the official record, character by character.
Check how long the name has been in use where public records show it, and whether the mail domain matches.
See where else they appear.
Note what they say about who contracts and where.
Research reports what can be established from public and provided sources. It is not a guarantee about a counterparty's future conduct and not legal advice.
It tells you about the site's cost. Look at what it commits to.
Basic checks need none. Treat any technical finding as a prompt for a question.
No; ask for it. The point is to test claims, not to assume the opposite.
No obligation. We read your request and reply with a straight answer.
Tell us what you need to find out and by when. We confirm scope before any work starts.
Request research