File scan report
Verdict Safe
Is this email message safe? Yes, no threats found.
Clean scan results across 61 engines with no detections; standard Outlook .msg email file shows no malicious indicators.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This file is safe based on comprehensive clean scans. Proceed with normal handling, but extract and scan any attachments separately as a precaution for email files.
Good practice2 tips
We found nothing harmful in this file.
Open it only after checking with the sender through a phone number or address you already have.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 61 flagged
- Flagged 0
- No detection 61
- No result 13
- Code signing Not applicable
- Test run Not run
- First seen 5mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The antivirus engines reports zero threats from 61 scanning engines, including major ones like BitDefender and Kaspersky. This is a common Outlook message file with no suspicious behavior, signing issues, or external intel hits. Despite being it appears benign.
High engine coverage returned universally clean results, with 17 major antivirus engines explicitly reporting clean. The file is a standard Outlook .msg format, a prevalent commodity type for email storage, lacking any rule triggers or filename red flags. No data from the test run exists, but absence of files it created, malicious contacts, or intel corroboration supports safety. Newness introduces minor uncertainty, but overwhelming clean signals dominate.
What We Detected
No detections from the antivirus engines: 0/61 engines flagged threats, including major antivirus engines (Avast, AVG, Avira, BitDefender, DrWeb, Emsisoft, ESET-NOD32, F-Secure, Fortinet, GData, Ikarus, Kaspersky, Microsoft).
Threat Behavior
No sandbox behavior recorded; no dropped files, malicious hosts contacted, or offensive techniques observed. Unsigned but no brand mismatch or adversarial input.
Static Analysis
Outlook .msg file, rare and prevalence, no PE entropy/packing (non-executable). No YARAify/CIRCL hits.
What To Do Now
Safe to handle; scan attachments if extracted. Monitor for anomalies.
Where this verdict could be wrong2 caveats
- behaviour=null (no sandbox data) — embedded attachments or macros in .msg file not dynamically analyzed.
- No similarHashes[] — lacks RAG grounding from prior verdicts on matching import-table fingerprint/signer.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0 malicious detections (61/61 engines reporting)
- 17 tier1ReportedClean
- Standard Outlook fileType
- No triggeredHeuristics
- No externalIntel hits
- File (firstSeen='May 6, 2026', it was first seen on May 6, 2026)
- Unsigned (the file is unsigned)
- No sandbox behaviour data
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 61 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- File name
- Email message
- Format
- Outlook
- Size
- 346.6 kB
- Code signing
- Not applicable to this file type
- Last analyzed
- May 6, 2026, 6:51 PM UTC
- SHA-256
7da855c87bbc5670c647586ff446ed8c62d8dfb8defd8dc5e7010068257d70fd- SHA-1
409177c735d56c202e410ad989cdfbf4d39d5c75- MD5
32989173770fa7bcbd2b619acf8f3cd4
First scanned
Includes every engine result (74) and how widely the file has been seen.
Show the technical evidenceChapter 04
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is this email message safe?
What is this email message?
How many antivirus engines detected this email message?
What is the SHA-256 hash of this email message?
Is it safe to open this email message?
How up to date is this analysis of this email message?
Community
Member reviews and reports for this exact file hash.