Triage your first phishing report

A user just clicked Report Phishing, and the ticket is yours. This guide shows you how to decide, quickly and safely, whether the email is malicious, harmless, or somewhere in between, and what to do next.

Go to the 10-step procedure

Two senders. One is fake. Can you tell which?

helpdesk@microsoft.com

helpdesk@rnicrosoft.com

Show the answer

The second one. It starts with r n, not m. Look-alike domains are why this guide teaches you to check evidence instead of trusting your eyes.

Who this guide is for

You are a junior security analyst, often called a Tier 1 or SOC (Security Operations Center) analyst, in your first months on the job. You may also be an IT help-desk technician who has been handed reported emails, or a student preparing for a SOC role. The guide assumes you:

What you will be able to do

By the end of the guide, you will be able to answer the three questions behind every phishing ticket:

  1. Is it malicious?
  2. Who else received it?
  3. Did anyone act on it?

This guide does not cover full incident response after an account is compromised, malware reverse engineering, or building email filters. When you reach those situations, the procedure tells you to escalate.

How to use this guide

  1. If you are new, start with Key Terms. Every later page uses those words.
  2. Read What the Research Says once to understand why this work matters.
  3. Keep Step-by-Step Triage open while you work a real ticket.
  4. See the steps applied in the Worked Example.
  5. Check the FAQ & Troubleshooting page when something does not match the steps.
Your playbook comes first

Always follow your organization's policies and escalation contacts. Where this guide and your team's playbook disagree, your playbook wins.

Last updated: October 2026