FAQ and troubleshooting

These are the questions new analysts ask most often. Select a question to see the answer.

Common questions

What if SPF, DKIM, and DMARC all pass? Is the email safe?

Not necessarily. A pass only proves that the sending domain authorized the message. Attackers register their own look-alike domains and set up authentication correctly. Always check which domain passed, and whether it actually belongs to the claimed sender.

The email came from a real coworker or vendor. Can I trust it?

Not automatically. The sender's real account may be compromised, or the attacker may have hijacked an existing email thread. Verify unusual requests through a known phone number, and escalate if you suspect a compromised account.

There is no link or attachment. Can I close it as harmless?

No. Business email compromise and callback phishing often contain only text or a phone number. Judge the request itself: payment changes, gift cards, and urgent transfers are high risk.

How do I know whether it's one of our own phishing simulations?

Ask your team how simulations are identified. Many simulation platforms add a special header or send from known domains. Don't tell the reporter it's a test until you're sure.

Should I reply to the sender to see what happens?

Never. Replying confirms that the mailbox is active and may alert the attacker.

Is it okay to upload the attachment to VirusTotal?

Search by file hash first. Uploading shares the file with the service's community, which can expose company data. Follow your organization's policy.

How long should triage take?

Most reports take 10 to 20 minutes. If you are past 30 minutes and still unsure, mark the email Suspicious, quarantine it, and ask for a second opinion.

Troubleshooting

Problems you may run into during triage
ProblemLikely causeWhat to do
The headers are missingThe reporter forwarded the email or sent a screenshotPull the original from the email security console, or ask the reporter to use the Report button
A URL scanner says “clean,” but it looks like a fake login pageThe site is new, or it shows different content to scannersTrust what you see in the sandbox; new domains often have no reputation yet
The link redirects several timesAttackers chain redirects to hide the final pageFollow the full chain in a sandbox, and record the final URL as the IOC
The sandbox page is blank or shows an errorThe site is offline, or it blocks sandboxes by location or device typeNote it as inconclusive; try another sandbox or escalate
The user says they clicked but “didn't type anything”They may not remember correctlyCheck proxy logs and sign-in logs; when unsure, escalate
Hundreds of people received itA large campaignEscalate right away; bulk removal usually needs senior approval
You aren't sure of the classificationNormal for a new analystMark it Suspicious, quarantine it, and ask for a second opinion. Asking is better than guessing.