DMARC guide

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.

Spoofed email example

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.

Example authentication results for legitimate and spoofed email with the same From address.
CheckLegitimate emailSpoofed email
Fromsupport@acme.example
Sending server198.51.100.10203.0.113.20
Server the company allows (SPF)AllowedNot allowed
Valid signature for the company domain (DKIM)PresentNot present
DMARC resultPassFail

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.

Next guide

Prepare your DMARC policy

Follow this guide to collect RUA reports, check sending servers and authentication, then prepare quarantine and reject policies.

DMARC setup guide

Check your company's domain settings now

Enter your company domain to see its DMARC policy and whether it requests quarantine or rejection.