Symptoms

Is this email phishing, spam, or genuine?

Check a strange email without following its links: verify the request, inspect sender details, and understand Browser Guard, local checks, VirusTotal, and urlscan.io limits.

A strange email can be phishing, unwanted advertising, a genuine notification, or a message from an account someone else now controls. Receiving it is not evidence that your computer is infected. The useful question is whether the sender’s identity and the requested action can be verified without trusting the message itself.

Begin by leaving links, attachments, QR codes, reply buttons, and contact details in the message unused. Do not send a password, verification code, document, or payment to see what happens. If this involves work or school data, use the organization’s reporting process before moving the message to any external analysis service.

First establish what you already did

Your situationPriorityWhat to avoid
Received the email and took no actionVerify the request through a known independent routeTreating receipt as proof of device infection
Opened the message without following its requestInspect details and report if deceptiveReopening links to reproduce the behavior
Followed a link without entering informationClose it; note downloads, permissions, or unexpected behaviorReturning to check whether it still works
Entered a password, code, or approved a sign-inRecover the affected account from a trusted deviceWaiting for a reputation report to confirm exposure
Opened an attachment or ran downloaded softwareRecord what happened and assess the deviceRunning it again or restoring a quarantined file
Sent money or sensitive informationContact the relevant organization through a known route and seek incident helpUsing the email’s callback number

These are different exposure levels. A scanner may help investigate a downloaded file, but it cannot recover a password you typed into a fake form or reverse an authorized payment. Use account recovery or device diagnosis according to what actually happened.

Verify the request outside the message

Open the service through a saved bookmark or its known official app. Check the account’s notification, order, or billing area there. For a request from someone you know, contact them using a number or conversation you already had before this email. Do not rely on the Reply address or a new number included in the message.

Both Google’s phishing guidance and Microsoft’s guidance recommend independent confirmation. This is particularly valuable for payment-detail changes, unexpected invoices, account closures, shared documents, and urgent requests from colleagues.

A message can use a real logo, your name, correct order details, or polished language and still be deceptive. Conversely, a spelling mistake alone does not establish phishing. Judge the requested action and independently confirmed context. If you cannot confirm the request, you do not have to act on it merely because the email sets a deadline.

Inspect the visible sender and destination locally

Expand the sender details in the mail app. Compare the displayed name with the actual From address and any Reply-To address. An unfamiliar reply destination deserves explanation, but legitimate services also use separate delivery and reply addresses. A recognizable From address can be forged, and a real account can be compromised.

On a desktop computer, hover over a link to inspect the shown destination without clicking. You can copy the link into a plain text editor if your mail app provides that option. Keep it as text; do not paste it into a browser address bar or a tool that automatically opens it. A shortened or rewritten tracking link may conceal a later destination, so a local preview is incomplete evidence.

Read the hostname, not just a brand name anywhere in the string. In the invented text https://accounts.example.com.verify.invalid/login, the hostname belongs under verify.invalid, not example.com. In https://verify.invalid/?next=example.com, the familiar domain is a query value. These reserved-domain examples illustrate structure; they are not sites to visit. HTTPS protects a connection to its destination and does not establish that the destination is the organization you intended.

If a QR code or attachment prevents you inspecting the request easily, use the independent route instead. Do not scan the code or open an attachment just to obtain more clues.

View original headers without uploading the message

Headers provide delivery and authentication context. They do not provide a simple certificate that an email is truthful. Keep the original message available for your provider or administrator; do not post full headers publicly, since they can contain personal addresses and infrastructure details.

For Gmail on a computer, Google’s header instructions describe opening the message’s More menu next to Reply and choosing Show original. Review the original locally. The sender-details arrow also exposes mailed-by and signed-by information in Google’s authentication guidance.

For new Outlook, Microsoft documents More actions → View → View message details. Classic Outlook for Windows uses File → Properties → Internet headers after opening the message in its own window. Use the instructions for your actual app; menus differ between clients.

The fields answer different questions:

  • SPF: whether the sending server is authorized for the envelope sender’s domain, which can differ from the visible From address.
  • DKIM: whether a domain’s signature verifies for the signed message elements. Read the signing domain rather than only the word pass.
  • DMARC: whether an authenticated SPF or DKIM identity aligns with the visible From domain, subject to the domain’s policy.
  • Reply-To and Return-Path: reply and delivery/bounce context. Differences can be legitimate and need interpretation.

Microsoft’s authentication explanation describes the interaction and forwarding limitations. Use your receiving provider’s authentication display or trusted results, not an arbitrary pasted header line as a verdict. A deceptive sender can authenticate its own lookalike domain; a compromised legitimate sender can also pass. Forwarding or mailing-list changes can disrupt authentication for genuine messages. Neither pass nor fail alone settles whether the request is safe.

Use VirusTotal only after considering privacy

VirusTotal can supply additional reputation evidence for a file fingerprint or a public URL/domain. It does not verify that an invoice is owed, that a colleague intended a request, or that a newly created phishing page has already been identified.

Read the current search documentation before querying anything. It warns that web indicators submitted or queried can be scanned and added to the shared dataset. Searching a URL is not a private way to check it. Avoid private document links, password-reset URLs, invitation tokens, internal hostnames, recipient-specific tracking links, and anything containing personal or confidential information. Removing a token changes what you are checking; a result for the bare domain is not a result for the original link.

For an attachment already saved without execution, a local SHA-256 calculation can identify its bytes without sending the file. On Windows, Microsoft’s Get-FileHash documentation supports this example:

Get-FileHash -LiteralPath 'C:\Users\YourName\Downloads\attachment.pdf' -Algorithm SHA256

Replace the illustrative path with the exact existing file. Hashing reads it; it does not open it in its associated application. Do not download or restore a blocked attachment just to follow this example. A hash identifies bytes, not legitimacy, and changing the filename does not change that fingerprint.

An authorized hash lookup can retrieve an existing file report without uploading its contents. The query still leaves the device, and applicable organizational restrictions remain. If the hash is unknown, do not upload the message or attachment merely to fill that gap. VirusTotal’s sharing explanation says ordinary reports and submitted content may be shared with its community, partners, and qualified customers. Zero detections is not proof of safety; inspect the object and report date, and retain independent confirmation as the deciding step.

Use urlscan.io to inspect a website, with sharing in mind

urlscan.io visits a submitted address in its own automated browser and records what that visit loads. Its report can provide a screenshot, the contacted domains and resources, and page observations. This lets you inspect a recorded visit without opening the suspect destination in your own browser. It still contacts the destination; it is not a purely local text check.

Start with the local hostname checks above and independent confirmation. For additional evidence, look for an existing report for a non-sensitive public domain before considering a new scan. A report for one page or the bare domain does not establish what a different path or recipient-specific link does. Avoid entering personal links into search fields, too: a query still goes to an external service. Do not submit an entire email, attachment, or full headers to this website-scanning service.

Before any new submission, read urlscan’s visibility documentation:

VisibilityWho can discover or access itDecision for email links
PublicVisible in public search and the front pageOnly consider genuinely public, non-sensitive addresses
UnlistedHidden from public search, but visible to vetted researchers and companies using urlscan ProDo not treat this as private
PrivateLimited in discovery; someone with the scan ID can still open the resultProtect the report link and remember that the service still visits the destination

Private controls report visibility, not whether urlscan receives the address or accesses its content. Keep password-reset links, sign-in tokens, private documents, invitation links, internal addresses, and recipient-specific tracking URLs out of submissions. Because the scanner visits the URL, a one-use or action-bearing link could also be activated or disclose who received it. If the available account or submission screen does not offer an appropriate visibility choice, stop rather than settling for Public or Unlisted. For work mail, use the organization’s process instead of making that decision yourself.

For a non-sensitive public address that you are authorized to analyze, a useful workflow is:

  1. Check the visibility before submitting, rather than trying to hide the report afterward.
  2. Read the recorded address and scan time. Inspect any redirection and the final destination shown in the report.
  3. Review the screenshot and contacted domains as context. Do not use the report’s live-site links to visit the suspicious destination, or download files it recorded.
  4. Return to independent confirmation. A copied login design or a familiar host does not verify the email’s sender or its requested action.

The urlscan FAQ describes reports as snapshots at the time of scanning, rather than continuously updated checks. Its phishing verdicts can miss cases or produce false positives, and recorded file downloads are not an analysis of whether those files are malicious. A blank page, no warning, or an old apparently benign report is not a safety certificate. The page may also behave differently for the scanner than for you. Do not use a report as a reason to enter credentials into the email’s link.

Browser Guard and existing browser protections

Malwarebytes Browser Guard is an optional browsing extension that the publisher describes as blocking scams, phishing attempts, malicious sites, ads, and trackers. Its official page links to Chrome, Edge, Firefox, and Safari installations. Use those publisher links and review the actual browser/edition before installing; do not accept an extension offered by the suspicious message itself.

Treat it as browsing protection, not an email authentication tool. It cannot establish that an invoice is owed or that a real colleague intended a message. No block does not make a page safe; a block deserves investigation rather than an automatic exception. Do not revisit a suspect link to test whether the extension catches it, and do not disable protection just because the page asks you to.

The current product page has Free and Premium feature columns. Check the specific feature and your plan rather than assuming every capability advertised applies to the free extension in every browser. Its permission explanation describes website, history, download, and some clipboard access, depending on browser and optional features. That permission guide covers Chrome, Edge, and Firefox; check Safari’s own listing for its access. The privacy policy describes collection including blocked-page URLs and excluded domains. Browser Guard should not be presented as a completely local or data-free link checker.

Keep existing protections enabled as well: Chrome Safe Browsing and Microsoft Defender SmartScreen in Edge provide warning and reputation checks. Bitwarden’s domain-aware login suggestions can help you pause at an unfamiliar address, but autofill is not proof of legitimacy. See the browser extension guide to choose by purpose and avoid overlapping blockers. Device antivirus, browser filtering, and confirming a message each address different parts of the problem.

Handle attachments and choose a response

Use the attachment safety guide for a fuller decision path: expected purpose, full file type, mail-provider blocks, Office protections, local checks, and what changes if you already opened or ran the file.

For files already present, review the full filename and extension, origin, and expected purpose without opening them. A file presented as a document might be executable or archived content. Do not enable macros, remove protective warnings, or enter an archive password simply because the email tells you that security checks are preventing delivery. Use your existing supported antivirus for local investigation when appropriate; on Windows, follow the scan guide. A local scan still cannot authenticate the sender’s request.

If the message is deceptive, use your provider’s phishing-report control. Gmail documents More → Report phishing; Microsoft documents Report → Report phishing in supported Outlook interfaces. For ordinary unwanted bulk mail, use the spam/junk route instead. Follow your administrator’s instructions for managed mailboxes; do not forward suspicious content around to ask everyone to try it. Reporting may send the message to the provider or organization, so it is different from the local checks above.

If you already exposed credentials or approved unexpected access, begin account recovery immediately through a trusted device and the official service. If you ran software, preserve the relevant details and assess the device. If money or financial information was involved, use an independently verified contact route for the relevant institution. A reputation lookup should not delay those actions.

This guide was researched and edited on 6 October 2026. No email, attachment, URL, or hash was submitted to an analysis service for this article, and no phishing or malware experiment was performed.

A VPN can change how a connection is routed; it cannot authenticate this sender or payment request. Read the VPN privacy guide for that distinction, and keep using independent confirmation for the email.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy