How to Know If Someone Is Real Online (or a Catfish): 9 Checks

This guide covers online contacts from dating apps, social media, games and forums. Its goal is a decision you can act on, not a verdict about a stranger. For photo-specific methods, use the dating image-search comparison; for one app's badges and reporting, use the Tinder guide.

1. Slow the interaction. A deadline in a message does not require an immediate reply.
2. Check the request first. Protect money, passwords, one-time codes, documents and device access.
3. Preserve relevant evidence. Keep the profile link, request, date and payment reference if safe.
4. Choose one public claim that matters. Use an independent official source when one can answer it.
5. Use image search only for a photo-source question. Upload only your own image or one you have permission to search.
6. Consider face search only if necessary. A specific different-photo source question must justify the additional upload.
7. Read the original page. Record what its caption and context support, leaving account control unresolved.
8. Offer an optional call or safe meeting plan. Both people can decline; neither establishes identity or intent.
9. Stop when the next action is clear. Decline, pause, report or continue cautiously without forcing certainty.

If a limited photo question remains, the public photo-source guide explains possible routes. If your own photos are being used, go directly to the photo-misuse reporting checklist.

The FTC advises against sending money or gifts to an online love interest you have not met. Australian eSafety guidance covers meeting and online-contact precautions. For Australian intimate-image harm, use eSafety's reporting route; elsewhere, use your local specialist service.

A photo lookup is not a recovery step for an exposed password or a pending transfer. Contact the affected provider first, even if you have only a partial record. Recovery is not guaranteed, but an unresolved identity does not prevent you from requesting help.

Catfishing means using a false online identity, but the label is less useful than the behavior you can describe. Money requests, pressure to conceal a transfer, threats and attempts to obtain account access give you a concrete reason to act.

You can decline a request without proving that the other person intended harm. An ordinary explanation for a missing detail also does not oblige you to keep talking. Keep decisions grounded in your boundaries rather than a tally of weak clues.

Keep the account URL or handle, the specific request, relevant dates and any payment confirmation. Record what happened separately from what you suspect. For example, “the account asked for a transfer on Tuesday” is an observation; a name from a search result is not evidence of who sent that request.

• Account and platform: where the interaction occurred.
• Event: the payment, code, link or threat and when it occurred.
• Exposure: what you actually sent or shared.
• Action: provider contacted, report number and next follow-up.
• Unresolved point: any claim you could not confirm.

You can copy this checklist into a private note or print it. Leave out unrelated relatives, addresses, identity documents and other people's contact details. Store sensitive originals securely and send them only through the official route that needs them.

For a professional or recruiting approach, use the LinkedIn claim-and-request guide. Its useful question is whether an independently found employer source confirms a role or request, not whether a face-search result establishes someone's employment history.

A reverse image search may find copies or visually related pictures. Open a relevant page and read the caption, publisher and date. A face-focused search may return candidates across different photos, but a resemblance score does not establish account ownership.

Choose a tool only after writing a source question that matters. Google's help describes image-search results; the method comparison explains when different-photo candidates might be relevant. If the decision is already to refuse a transfer, another image upload adds no necessary step.

Do not use a photo's polish or an apparent visual defect to declare it real or generated. Our AI-image guide explains the limitations. With any method, no useful result leaves the question open. A saved celebrity example illustrates an output format only and cannot establish who controls your conversation.

A short in-app call can add conversational context if both people want it. It cannot prove a legal name, job, background or future intentions. Refusing a call can have ordinary privacy, safety or accessibility reasons.

Do not demand an identity document, an intimate image, a forced pose or a view of someone's home. If a call is unavailable and you are uncomfortable continuing, you may pause. You do not need to turn your uncertainty into a test another person must pass.

For a first meeting, use the action card above and the platform's own current advice, such as Tinder's safety tips. Keep your transport and departure independent of the person you are meeting. Search results should not change those precautions.

Hypothetical example, not a customer case: after several weeks of messages, a contact asks for money to release a delayed travel booking. You have already made one transfer. They now want another payment and ask you not to tell your bank why.

Start with the exposed money: call your bank through its usual app or number, explain the transfer and ask about stopping further loss. Save the payment receipt and the messages requesting secrecy. The bank needs transaction facts; you do not need a real-world name for the operator before calling.

An optional image lookup returns no useful page. Record that the photo question is unresolved and stop searching. Report the account's request through the platform, retain the reference, and tell a trusted person what support would help. Whether the photo is original, copied or generated does not change the payment boundary.

If you are helping someone, offer to sit with them while they take the next step. Avoid demanding that they admit the entire relationship was false. Scamwatch's support guidance favours practical, non-blaming help.

Stop collecting information when the relevant claim is answered, remains unresolved after a proportionate check, or would not change your action. More copied pages are not necessarily more evidence. Do not contact people found in image results or ask a crowd to identify them.

Use each reporting route for its role: the platform for the account and content, the provider for exposed funds or access, and your country's official fraud or cybercrime channel for the incident. Australian readers can use Scamwatch's recovery guide, which links bank, police and IDCARE support. A platform report does not contact these services automatically.

Decline offers from strangers who promise to recover funds for a fee. Keep case numbers and follow-up instructions in your private record. You may leave the identity question unanswered and still complete the useful work: secure access, stop further exposure and get support.