How to Assess a Potential Phishing Message
A practical guide to evaluating suspicious messages by weighing their content, sender, links, attachments, and context—and verifying concerns without relying on any single clue.
Weigh the Clues, Then Verify Independently
What phishing tries to do
Phishing is a deceptive message intended to persuade someone to disclose information, send money, or take an unsafe action—for example, opening a harmful link or file. It can arrive by email, text, or social media. Because a message can contain mixed signals, assess it as a whole: consider its request, sender, links, attachments, and fit with the circumstances rather than relying on one detail.
Weigh the clues together
Start with the request and the pressure around it. Urgency, threats of account closure, unexpected prizes, or appeals to fear or curiosity deserve attention. Be especially cautious about requests for passwords, payment details, verification codes, or other sensitive information. Generic greetings, missing or inconsistent details, and spelling or formatting errors may add to concern—but style alone is not a reliable test. Attackers can write convincingly, and legitimate messages can be brief, automated, or imperfect.
Check the full sender address or phone number, not just the displayed name. Look for a look-alike domain, altered spelling, or contact details that do not fit the person or organization claimed. Compare them with details you already know to be genuine. Even a familiar address is not conclusive: sender information can be imitated, and a legitimate account may be compromised.
For a link, inspect its actual destination using your device’s safe preview method. Check the domain for misspellings or unexpected additions. Be cautious with shortened or unfamiliar links, and with unexpected sign-in or payment pages. A long or unfamiliar URL is not automatically malicious, just as a familiar-looking link is not automatically safe. If uncertain, use a known website address or a trusted contact channel instead of the message’s link.
Treat attachments in context. Ask whether you were expecting the file, whether its type and circumstances make sense, and whether the message is pressuring you to open it immediately or enable macros, content, or other active features. An unexpected attachment merits caution, but attachments are not inherently unsafe; confirm a surprising file through a separate trusted channel before opening it.
Finally, check whether the message fits an account you have, an expected transaction or shared file, and the way you usually receive such requests. Plausible details or a match to a current event do not authenticate a message: a message about a delivery, invoice, or work task can still be fraudulent. Context is one clue, not proof.
A hypothetical application
Suppose a text claims that a delivery needs an urgent fee and includes a payment link. The urgency and unexpected payment request are reasons to pause, not proof by themselves that the text is fraudulent. Check whether you were expecting a delivery; inspect the full sender number and the link’s destination with a safe preview. Do not use the message’s link to investigate. If the request remains unexpected or uncertain, contact the delivery service through a website address or phone number you already trust. This checks the claim without treating any one clue as a verdict.
Verify and report safely
When an unexpected message asks for a sensitive action, pause. Do not reply, click, or open an attachment as a way to investigate. Instead, contact the person or organization using a phone number, website, or other channel you already trust—not contact details supplied in the suspicious message. If the message seems suspicious, follow your organization’s reporting process or use the service’s report-spam or report-phishing feature.
The key is to weigh indicators together and verify important requests independently. No single clue proves a message is fraudulent, and no single reassuring detail proves it is safe.