How spoofed email gets sent
See how email spoofing your company's address gets sent, and how to ask Gmail to block it.
The sender can choose any From address
Just as someone can put any return address on an envelope, an email sender can put your company's address in the From field.
Gmail needs to verify that email came from your authorized servers
Publish the list of servers allowed to send email for your domain (SPF) and the public keys for verifying email signatures (DKIM) in your domain's DNS.
| Check | Legitimate email | Spoofed email |
|---|---|---|
| From | support@acme.example | |
| Sending server | 198.51.100.10 | 203.0.113.20 |
| Server the company allows (SPF) | Allowed | Not allowed |
| Valid signature for the company domain (DKIM) | Present | Not present |
| DMARC result | Pass | Fail |
DMARC passes if SPF or DKIM passes with a domain that aligns with the From domain. Failed authentication doesn’t always mean spoofing.
You need to ask Gmail to block spoofed email
Gmail doesn't always block email when the details don't match. A legitimate sending server may have been left off the list by mistake. Use the DMARC p value to tell Gmail how you want email with mismatched details handled.
p=none- Take no further action; just send the results in RUA reports.
p=quarantine- Send email that doesn't match to spam instead of the inbox.
p=reject- Treat email that doesn't match as spoofed and block it.
To request RUA reports, you need a reporting address in rua, regardless of the p value.
Check your company's domain settings now
Enter your company domain to see its DMARC policy and whether it requests quarantine or rejection.