Mailbox providers
Gmail Warnings: 'This Message Seems Dangerous' and 'Be Careful With This Message'
Gmail shows these banners when it suspects phishing, spoofing or unauthenticated mail. As a sender, fix authentication, then look at links and content.
On this page
Gmail shows "This message seems dangerous" (a red banner) when its filters think a message is likely phishing or malware, and "Be careful with this message" (a yellow banner) when something about the message looks off but not clearly malicious, often because Gmail can't confirm who sent it. If your recipients are seeing either one on mail from you, start with authentication: make sure every message passes SPF or DKIM for your own From domain and passes DMARC. Then look at your links, attachments and anything that makes your mail resemble a spoof.
These banners are not the same as a spam folder placement. The message is in the inbox, but Gmail is telling the reader not to trust it. For a sender, that can be worse than spam: people see your brand next to a warning.
What the warnings mean
Gmail doesn't publish a full catalog of its banners, and the explanatory text underneath them changes. What Google does say is that "when we identify that an email may be phishing or suspicious, we might show a warning or move the email to Spam." In practice the banners you'll hear about fall into a few groups:
| Banner | What Gmail is reacting to | How worried to be |
|---|---|---|
| "This message seems dangerous" (red) | Content or links that match known phishing or malware patterns, or a strong spoofing signal | Very. Recipients are told not to click or reply. |
| "Be careful with this message" (yellow) | Gmail can't verify the sender, the sender looks like it's impersonating someone, or the message has risky elements | Moderate. Usually fixable on your side. |
| A question mark instead of the sender's photo | The message isn't authenticated | A smaller version of the same signal |
| Banners on mail to a company using Google Workspace | The recipient's admin turned on extra phishing and malware protections | Depends on their settings, not just yours |
Google's help page on authentication is direct about the question mark: "If you see a question mark next to the sender's name, the message isn't authenticated," meaning "Gmail doesn't know if the message is coming from the person who appears to be sending it." The yellow banner is often the louder version of that same problem.
Common causes (most likely first)
1. Missing or misaligned authentication
This is the one I'd check first, every time. If a message arrives without a passing SPF or DKIM result for your domain, Gmail has no way to tell it apart from someone spoofing you. The usual culprits:
- A third-party tool (CRM, help desk, billing system, survey platform) sends as
you@example.combut signs DKIM with its own domain and uses its own return path. SPF and DKIM pass, but neither aligns with your From domain, so DMARC fails. - DKIM was never enabled for your domain in Google Workspace or Microsoft 365.
- Your SPF record is broken, often because it went past the 10 DNS lookup limit.
Google's sender guidelines require every sender to set up SPF or DKIM, and bulk senders (more than 5,000 messages a day to Gmail) to have SPF, DKIM and DMARC with alignment. Run your domain through the email checker, and see DMARC fail if alignment is the problem.
2. Your mail looks like a spoof of someone else
Gmail compares the display name and From address against senders the recipient knows and well-known brands. A display name like "PayPal Billing" on mail from a domain that isn't PayPal's, or a From address on a lookalike domain (examp1e.com), will draw a warning. The same goes for sending "from" a free mailbox domain like gmail.com through a third-party platform. Google's guidelines explicitly say not to impersonate Gmail From headers.
3. Risky links
Link shorteners, redirect chains, raw IP addresses in URLs, freshly registered link domains, and click-tracking domains that don't match your brand all raise suspicion. If one of your link domains is on a domain blocklist like the Spamhaus DBL, expect worse than a banner. Check every domain in the message, not just your sending domain.
4. Attachments and forms
Encrypted (password-protected) attachments can't be scanned, and documents with scripts or macros are a classic malware delivery method. Workspace admins can set Gmail to show a warning for both; Google's admin documentation lists "Keep email in inbox and show warning" as the default action for encrypted attachments and attachments with scripts from untrusted senders. Asking for passwords or payment details in the body of an email, or linking to a login page, also fits phishing patterns.
5. The recipient's own Workspace settings
If your recipients are at companies using Google Workspace, their admins can turn on protections against spoofing of domain names, employee names and unauthenticated email. With the "warning" action, Google says "the user sees a warning banner about the message." That means two senders with identical setups can get different results at different companies. Google also notes these banners only appear in Gmail on the web, not in third-party apps.
6. Security test campaigns
If your security team runs phishing simulations from your real domain, stop. Google's sender guidelines say not to send test phishing messages or test campaigns from your domain, because it can hurt your domain's reputation.
How to fix it
- Get a real example. Ask a recipient who saw the banner to forward it as an attachment, or open it in Gmail and use More, then "Show original." Note which banner they saw and the line of text underneath it.
- Read the authentication results. In the original message, look at the SPF, DKIM and DMARC results and the domains they were evaluated for. Paste the header into the header analyzer if it's easier. You want DMARC: PASS, with DKIM signed by your From domain (or a subdomain of it).
- Fix every sending source. For each platform that sends as your domain, set up DKIM with your domain and, where the platform supports it, a custom return path on your domain. Fix SPF if it's over the lookup limit; the SPF analyzer counts them.
- Publish DMARC. If you don't have one, start with
p=noneand a reporting address using the DMARC generator. The reports will show you senders you forgot about. - Clean up the message. Use your own branded link domains, drop URL shorteners, avoid sending attachments to people who didn't ask for them (link to a page on your site instead), and make sure the display name matches who the mail is actually from.
- Check your domains for listings. Look up your sending domain, link domains and image hosts on the major domain blocklists.
How to confirm it's fixed
Send the same message to a few Gmail accounts you control, including one on Google Workspace if you have it. Open "Show original" and confirm SPF, DKIM and DMARC all pass for your domain. The question mark should be gone. Banners driven by content or links can take longer to clear because Gmail is reacting to patterns, not a single record, so check again over the next several sends.
How to keep it from coming back
Treat every new tool that sends email as your domain as an authentication project, not a checkbox. Keep a list of sending sources, watch your DMARC aggregate reports for new ones, and move toward an enforcing DMARC policy once everything legitimate passes. That also makes it harder for anyone else to send convincing mail in your name, which is often why your mail looked suspicious in the first place.
When to get help
If authentication passes cleanly and recipients still see the red banner, the cause is usually in your links, your domains' reputation or a past spoofing campaign against your brand, and that's worth a closer look. Get in touch.
FAQ
Can I ask Google to remove the warning from my emails?
No. There's no request form for senders. Recipients can mark an individual message as not spam for themselves, but the fix for everyone is on your side: authentication, links and content.
Why do some recipients see the warning and others don't?
Gmail evaluates each message against each recipient's history, and Workspace admins can add stricter settings for their own users. A banner at one company and not another usually points to the recipient's admin settings or their relationship with you.
Does the warning mean my emails are going to spam?
Not necessarily. A banner is shown on mail that was delivered, often to the inbox. But the same signals that trigger a banner, especially failed authentication, also hurt placement, so it's worth checking your overall Gmail delivery too.
My own internal emails are getting the warning. Why?
Usually someone is sending as your domain from a system that isn't authenticated, or mail is passing through a gateway or forwarding service that breaks DKIM. Check the original message's headers to see which server it came from.
Sources
Related guides
- Gmail Spam Rate Threshold: What 0.1% and 0.3% Really MeanGmail requires a spam rate below 0.3% and recommends below 0.1%, measured on inbox-delivered, DKIM-signed mail in Postmaster Tools. Here's what that means.
- How to Get Delisted by Microsoft (Outlook.com and Microsoft 365)Microsoft runs separate block lists for Outlook.com and Microsoft 365, each with its own removal process. Match your bounce code to the right one, then ask.
- Why Are Yahoo and AOL Blocking My Emails?Yahoo and AOL block or defer mail over complaints, weak authentication, bad lists, sudden volume spikes and poor IP reputation. Here's how to find which one.
- Why Do My Emails Go to Junk in Outlook and Hotmail?Outlook junks mail that fails authentication, comes from a low-reputation IP, or draws complaints. Here's how to read Microsoft's verdict and fix the cause.
- Why Is iCloud (Apple Mail) Blocking My Emails?iCloud blocks mail that fails authentication, comes from a poorly rated IP or domain, or trips its content filters. Read the bounce first, then fix the cause.
- Why Is Outlook (Hotmail, Outlook.com) Blocking My Emails?Outlook blocks mail for a few reasons: IP reputation, failed authentication, throttling or a banned IP. The bounce code tells you which and what to do.
Still stuck?
Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.