Scam OSINT: How to Check a Suspicious Message, Website or Company

Turn “this feels wrong” into a question you can investigate

Scam OSINT uses publicly available information and clues you legitimately possess to assess suspicious claims. The aim is a clearer account of what is known and what needs verification. It is not a machine verdict that a named person is a criminal.

Begin with the proposed action: send money, share documents, install software, move a conversation or change an established payment route. Then identify the claim that makes the request sound reasonable. “I work for your supplier” and “this is your supplier’s new website” need different checks.

Preserve the request as evidence, then break it apart

Keep the original message, relevant public URL and the time you received it. A screenshot is useful context, but a cropped image can omit the sender, date or surrounding conversation. Preserve the original where possible and work from a copy. Do not open a suspicious attachment or submit personal details merely to gather more evidence.

Test the hinge claim first

The hinge claim is the statement the request needs you to believe. If a person claims to represent your existing supplier, establishing whether an unrelated company with the same name exists is a detour. Focus on the claimed relationship.

1. Write the request in one sentence. Include what changed from the normal arrangement.
2. Identify the claimed authority. Record the business, role or relationship the sender relies on.
3. Find an independent reference. Use a known contact route, the appropriate public register or a source you locate separately.
4. Compare exact identifiers. Domain names, registered identifiers and full public profile URLs are usually more discriminating than a logo or display name.
5. Keep contradictions visible. Do not discard an inconvenient date or domain because most of the story appears consistent.
6. Record the remaining uncertainty. If a necessary relationship cannot be established, say so. An incomplete search is not a clearance.

Use the detailed company claim checklist, email workflow or phone guide for the clue that matters. Each asks a different question; repeating every lookup rarely strengthens the evidence.

Example: a polished website does not settle a changed request

Fictional exercise, not a live case or customer success story. A message says a supplier has changed its contact domain. The linked website looks professional, repeats the supplier’s address and displays an image of a registration document. The sender asks you to treat the change as urgent.

The website and document image repeat the sender’s story; they are not necessarily independent support for it. Your evidence note should distinguish the correct address from the unverified control of the new domain. The decisive next question is whether the established supplier confirms the change through an independently known route.

Urgency matters because it discourages verification, not because every urgent message is fraudulent. A new domain matters because it changes the relationship you must establish, not because every new website is a scam. This reasoning keeps a useful check from turning into a collection of unreliable rules.

When more results are just more copies

Several pages may reproduce the same complaint or company description. Trace them back to their origin. Treat a reposted allegation as one claim until you find independent evidence. Preserve the wording and attribution without presenting an accusation as your own conclusion.

Make the next review easier with OSINT Jet

When a case contains a website, message, number and public profiles, the difficulty is keeping the connections straight. OSINT Jet is designed to turn those inputs into a structured investigation with findings, relationship context, uncertainty and next steps. Include the exact request, the claimed affiliation and the details that conflict.

You are buying help organizing and investigating a case, not certainty about every person on the internet. Read the scam-review workflow and report options. If consequences are serious or the evidence is contradictory, a manual review request provides a route to a scoped human review.

Organize the clues behind a suspicious request

Finish with a decision record

Write three short statements: the claim you checked, the evidence that supports or contradicts it, and the unresolved step. Include source URLs and dates so someone else can review the work. Preserve relevant records if you need to contact a service provider or an appropriate reporting body; this research workflow does not itself recover funds or replace professional advice.

Can a clean search prove a website is safe?

No. A new or poorly covered site may have no visible complaints. Absence of a result describes the search, not the site’s trustworthiness.

Should I confront the person to get more information?

Direct contact can change the situation and introduce additional risk. This guide’s workflow is based on existing material, public sources and independent verification, rather than impersonation or provoking a response.