Read website observations as dated technical evidence. An encrypted connection does not settle whether the seller will fulfill your particular transaction.
Separate the connection from the transaction
HTTPS concerns the connection to a website. It does not establish that an item will arrive, that its description is accurate or that a merchant will honor a return. The FTC explicitly distinguishes site encryption from seller legitimacy. A lock symbol should not replace the rest of your purchase research.
Make two columns in your notes: technical questions and transaction questions. “Was HTTPS available for this domain?” belongs in the first. “Who handles an exchange for this item?” belongs in the second. Keeping them separate prevents a useful but narrow technical result from becoming a much broader endorsement.
Read the check date and the exact checked domain
ReviewList checks public DNS, available domain-registration information and HTTPS with certificate validation. Read the stored check date. The result describes an observation at that time, not continuous monitoring or a promise about every page on the site.
Write the domain exactly as shown. If a store sends you to another address, identify whether it is a payment service, a seller or something else before treating the original check as relevant. Do not assume that a company name, a similar-looking domain and a checkout hostname all identify the same organization.
Handle missing or unsuccessful observations carefully
An unavailable observation means the check did not establish that signal. It does not prove the merchant is fraudulent. Equally, finding public DNS only shows that public DNS information was found; it does not establish ownership of a business or the quality of its service. Domain registration timing is context rather than a merchant verdict.
For an illustrative research record, “HTTPS unavailable during the stored check; needs further verification” is more precise than “unsafe store.” If a technical uncertainty matters to the action you plan to take, resolve it before submitting information. Avoid assigning a confidence percentage that the underlying observations cannot support.
Add evidence that answers your purchase questions
Find the actual seller, the current item description, the applicable terms and a working contact route. Read customer accounts that resemble your intended order. ReviewList’s published feedback is partial, and collected feedback is kept separate from direct submissions. A company’s average cannot fill in a missing answer about your specific checkout or return.
Keep your final note modest: what was observed, what was reported by customers and what remains unknown. ReviewList does not provide a safety certificate, guarantee a refund or resolve transactions for merchants. Technical information is useful when it helps you ask a better question, not when it ends the investigation prematurely.
Technical signal versus purchase question
| Observation to record | Question it does not settle |
|---|---|
| HTTPS available at a dated check | Will the seller fulfill this particular order? |
| Public DNS found | Which organization is responsible for the transaction? |
| Registration information available | Are the products, service or current promises reliable? |
| No stored observation | Is there enough relevant information to make my decision? |
| Checkout uses a different domain | What role does that domain have, and which party am I paying? |
Questions and answers
Does ReviewList give websites a safety certificate?
No. Results describe dated public technical observations, not a guarantee of merchant legitimacy, product quality or transaction safety.
Does a new domain mean a shop is fraudulent?
No. Registration timing, missing information or limited feedback alone does not establish fraud. Record the gap and investigate relevant questions.
Can the check tell me whether a refund will be paid?
No. Technical configuration does not establish refund behavior. Identify the responsible seller and current terms; ReviewList does not arrange refunds.
Sources and scope
ReviewList publishes this guide to explain a practical research or review workflow. Linked sources support the specific external principles discussed; they are not endorsements of ReviewList. Current merchant terms and the details of a particular order may differ.
Editorial date: Oct 13, 2026. Suggest a factual correction.