How to Tell If an Email Is Phishing: A Practical Verification Checklist
A suspicious message does not need to look obviously fake. This checklist helps you verify the sender, inspect links and attachments, assess requests for money or credentials, and decide what to do without increasing your risk.
Overview
Phishing is a social-engineering attempt that uses email, webmail, messaging, or a related channel to persuade someone to reveal information, open a harmful file, approve a payment, or sign in through a fraudulent page. The message may imitate a colleague, supplier, bank, cloud service, delivery company, or internal IT team. Some attempts contain poor spelling and obvious warnings; others are carefully written and use copied branding.
The safest approach is to slow down and verify the request through an independent route. Do not use the phone number, link, reply address, or attachment supplied by the suspicious message until you have assessed it. If the email concerns an invoice, password, account warning, or urgent approval, compare it with information you already trust, such as a known contact record, an established internal directory, or the official website reached by typing its address yourself.
No single clue proves that an email is legitimate or malicious. A familiar logo can be copied, a real account can be compromised, and technical authentication results do not confirm that the request itself is safe. Treat the checklist as a set of signals that should be considered together.
What to track
1. The sender and reply-to details
Start with the complete sender address, not just the display name. Look for misspellings, extra words, unexpected domains, substituted characters, or a free-mail address where a business address would normally be expected. Be cautious with addresses that resemble a legitimate domain but use a different ending or a small variation.
Next, inspect the Reply-To field if your webmail interface shows it. A message can display one address while directing your reply to another. A mismatch is not automatically proof of fraud, but it is a reason to verify the request before responding. Also consider whether the sender normally contacts you about this subject and whether the tone matches their usual communication.
2. The request and its pressure tactics
Phishing messages often try to prevent careful review. Common pressure patterns include a short deadline, a threat of account closure, an unusual request from an executive, a demand for secrecy, or an instruction to bypass normal approval steps. Be especially cautious when a message asks for passwords, multifactor authentication codes, payment details, gift cards, cryptocurrency, payroll changes, or a transfer to a new bank account.
Urgency is not evidence that a request is genuine. If the request could cause financial, operational, or privacy harm, confirm it using a separate channel. For example, call a known number from your records or start a new message to a trusted address rather than replying to the suspicious email.
3. Links and destination addresses
Do not open a link merely to find out where it goes. On a computer, you may be able to hover over it and inspect the destination shown by your mail client. On a phone, use extra caution because the full address may be difficult to see. Watch for shortened URLs, unexpected subdomains, misspelled company names, unusual character strings, or a destination that does not match the service named in the message.
A secure connection indicator or an address beginning with HTTPS does not by itself make a page trustworthy. Legitimate encryption protects the connection; it does not prove who operates the website. If you need to access an account, open a fresh browser window and type the known service address or use a saved bookmark that you created previously.
4. Attachments, invoices, and QR codes
Unexpected attachments deserve the same scrutiny as links. Be cautious with executable files, compressed archives, documents that request macros or additional sign-in, and files whose names use double extensions or unusual characters. An invoice that appears to come from a known supplier should still be checked against your purchasing records and verified through an established contact.
QR codes can conceal the destination from the normal link preview process. Treat a QR code in an unexpected email like a clickable link: do not scan it until the request has been independently confirmed. If a message asks you to scan a code to “secure” an account or approve a login, use the service’s normal app or website instead.
5. Mail warnings and authentication results
Pay attention to warnings displayed by your webmail provider, browser, or security software. Labels such as external sender, suspicious message, or unsafe link are useful signals, but the absence of a warning is not a clean bill of health.
Technical headers may include SPF, DKIM, and DMARC results. These checks can help show whether a message was sent through systems authorized for a domain or whether its contents appear to have been altered in transit. They do not prove that the sender’s account was not compromised, that the request is appropriate, or that every link is safe. For high-risk messages, use authentication results as supporting evidence rather than the only verification step.
6. The context of the conversation
Review the thread history, but do not assume an existing conversation is safe. Attackers may insert themselves into a real thread after gaining access to an account or may imitate the subject and formatting of an earlier exchange. Check whether the timing, participants, and requested action make sense. If the message changes payment instructions or asks for sensitive information, verify the change outside the thread.
Cadence and checkpoints
Use the checklist whenever an email requests credentials, payment, confidential information, a new bank destination, an unusual file action, or an urgent exception to normal process. It is also useful before approving a request from an unfamiliar sender, even if the wording appears professional.
For individual inboxes, review your reporting and security habits at least quarterly. Confirm that you know how to report a suspicious message in your webmail provider, where account recovery options are maintained, and whether multifactor authentication or passkeys are available for important accounts. A separate guide to webmail two-factor authentication and passkeys can help with setup and recovery planning.
For teams, include a short phishing review in onboarding and recurring security training. Administrators can use a quarterly audit to check mailbox rules, forwarding settings, delegated access, authentication controls, and incident contacts. The webmail security audit and incident response checklist provides a broader framework for that review.
Keep a simple record of recurring observations: the sender impersonated, the request type, the delivery channel, the warning shown, whether a link or attachment was involved, and how the message was reported. Do not store unnecessary personal information or forward suspicious content more widely than needed.
How to interpret changes
A new sender domain, repeated invoice theme, increase in QR-code messages, or sudden change in the language used against your team may indicate that your verification guidance needs to be refreshed. It does not establish who is behind the messages, so describe observations precisely rather than assigning blame.
Pay attention to combinations of signals. A familiar display name plus a new Reply-To address is more concerning than either detail alone. A legitimate-looking document combined with an unexpected request to sign in should be treated as high risk. A provider warning combined with an unfamiliar destination should normally end the interaction.
If you clicked a link, opened an unexpected file, entered credentials, or approved a payment, act promptly. Stop interacting with the message, disconnect a potentially affected device from networks if your organization’s procedure calls for it, and contact your IT or security team through a known channel. Change exposed passwords from a trusted device, review recent account activity, revoke unfamiliar sessions where the service allows it, and notify the relevant financial or service provider when a transaction or account is involved. Do not hide the event because an early report can improve the response.
For a message that is merely suspicious, use your webmail provider’s built-in phishing or spam reporting control when available, then delete it or retain it according to your organization’s policy. Avoid replying, clicking unsubscribe, downloading content, or forwarding the message to colleagues without a clear reporting purpose.
When to revisit
Revisit this checklist quarterly and whenever your email provider changes its warning labels, reporting controls, login flow, or security settings. Refresh team guidance after a new scam pattern appears in your inbox, such as altered payment instructions, fake document-sharing notices, QR-code requests, or impersonation of a known contact.
Update the checklist when your organization changes domains, mail routing, authentication controls, vendors, payment procedures, or approved collaboration tools. If staff report that webmail is not working, separate ordinary delivery or login problems from security alerts before changing settings or entering credentials. Likewise, confirm IMAP and SMTP settings only from trusted documentation when configuring a mail client; a suspicious message should never be the source of server details.
Before you approve a high-impact request, pause and run the practical sequence: inspect the complete sender and Reply-To address; identify the exact action requested; preview links without opening them; treat attachments and QR codes as untrusted; review any provider warning; verify the request through a separate known channel; report the message; and document what happened if an account, payment, or sensitive data may be involved. That routine is simple enough to repeat and specific enough to catch many phishing email signs before they become an incident.