How to tell if a text message is a scam

The short answer: A polished message can still be fraudulent, while a clumsy message can be real. The dependable question is whether the sender can be verified outside the message and whether the requested action creates avoidable risk.

Why writing quality does not establish who sent a text

The useful move is to separate what the claimant controls from evidence you can obtain independently. Names, logos, caller ID, screenshots and a polished page can all be copied. A saved telephone number, a typed official address, a known colleague or a protected transaction route changes the channel instead of merely inspecting the same claim again.

Risk also depends on consequence. Reading a public page is different from granting remote access, sending an identity document or approving an irreversible payment. As the cost of error rises, require stronger verification and prefer a step you can undo.

Warning signals to assess together

These clues become useful when they form a pattern. Treat each one as a prompt to verify, not as a verdict by itself.

• Unexpected urgency or a deadline invented inside the message

  Pair this observation with a separate check: Do not use the included link or telephone number.

• A link that bypasses the service's normal app or website

  Pair this observation with a separate check: Open the known app or type the organisation's address yourself.

• A request for codes, payment, identity details or secrecy

  Pair this observation with a separate check: Contact the person or organisation through a saved, published channel.

Do not use one clue as a verdict: No single typo, sender name or lock icon settles authenticity. Strong assessment uses multiple independent signals.

At this stage, the message red-flag checker can help separate pressure, secrecy and the requested action from the sender's identity.

Verify the sender without using the message's contact route

Keep the verification route separate from any contact detail or instruction supplied in the questionable message.

• Do not use the included link or telephone number

  This step tests the related concern: Unexpected urgency or a deadline invented inside the message.

• Open the known app or type the organisation's address yourself

  This step tests the related concern: A link that bypasses the service's normal app or website.

• Contact the person or organisation through a saved, published channel

  This step tests the related concern: A request for codes, payment, identity details or secrecy.

Decide what to do after verification

If the independent channel confirms the identity and request, ask whether the proposed method still gives you a record and recourse. Legitimate people and organisations should tolerate a proportionate verification step. Resistance, secrecy or a demand to bypass normal controls is new evidence, not an inconvenience to ignore.

If the evidence remains mixed, reduce exposure: do not send original documents when a redacted copy is enough, do not pay a deposit before verifying authority, and do not approve access broader than the task requires. “Not yet” is a valid decision when the missing fact matters.

The same tactic appears in the parcel-delivery message checklist, but the safest independent check changes with the channel.

What this verification cannot establish

This guide cannot authenticate a specific person, account, website or transaction. Interfaces and attack methods change, and legitimate situations sometimes contain unusual details. For an active loss, account compromise or safety threat, contact the relevant institution or official reporting service through a verified route.