1. Look for signals that agree

Check the precise profile address, its history, publicly linked websites and the consistency of its posts. A polished photograph, a large following or a recent account never settles the question on its own. Impersonators can copy pictures and biographies, while a genuine account may have little activity.

2. Confirm the request elsewhere

If a friend, business or organisation asks for money, a code or urgent action, contact them using a number or address you already had. Avoid the contact details supplied in the suspicious message. Open the official app or website yourself instead of following a received link.

3. Preserve evidence before reporting

Record the profile URL and date, then capture the messages and specific requests. Use the platform reporting tools and select impersonation when that option is available. Warn anyone who might have received the same message without amplifying the fraudulent link.

4. If someone copies your identity

Secure your real account and its email address first. Share a short warning from channels your contacts already know and ask them not to interact with the copy. If anyone sent personal information or money, keep the conversation and consult the reporting steps for their country.

Verify an account from a known starting point

Practice case: a profile resembling an association asks you to change payment details.

Base the decision on confirmation independent of the request, rather than profile resemblance alone.

A concrete example

Situation. An account using a friend’s photo asks for a code received by message. Even if the tone sounds familiar, the request needs checking outside that conversation.

How to try it. The recipient contacts the friend through a number or channel already known, without following the new profile’s link. They save the account address and message before reporting possible impersonation.

What to check next. If they already sent a code, they secure the affected account through official recovery and review active sessions.

Put this guide into practice

Compare the exact profile address, history and contact details with a known channel for the person. A familiar photo and identical name do not prove identity.

How to assess the result

Identity is confirmed independently of the suspicious profile before sharing anything.

Editorial exercise; adapt it to your situation and keep sensitive details out of your notes.

Compare displayed identity with the actual request

Fictional scenario and editorial method; no platform outcome is measured here.

Someone receives a request from a profile using a colleague’s name and photo. The message asks for an internal document.

Prepare the trial

Inspect the profile without sharing data and contact the colleague through an already used channel. Retain the suspicious profile link and request context.

Observe a useful outcome

Verification concerns the current request, not merely the colleague’s existence. Visual resemblance remains a clue rather than proof.

When to reconsider your approach

If the colleague does not confirm, do not send the document. Use appropriate reporting procedures rather than publishing an accusation containing private data.

Sources and method

This editorial synthesis draws on the sources below. Features may change by service and country.

WORLD SOCIAL NETWORKS · Suggest a correction.

Keep exploring

Recognise scams · Secure your account

A question before putting this into practice

Should I publicly accuse a profile I find suspicious?

Avoid turning uncertainty into an accusation. Verify through another channel, retain useful links and report using the service’s appropriate category. If warning contacts, describe the suspicious request and verification method without unnecessarily exposing a person.

Continue the process