DMARC
Ask Gmail to block spoofed email
Gmail can still show spoofed email to users. Use your DMARC record in DNS to ask Gmail to send spoofed email to spam or block it.
See spoofing activity in reports from Gmail
Review the sending server list in RUA reports (spoofing reports) to see spoofing activity.
Learn more- Email · 30 days
- 3,905
- Failed authentication
- 315
- Spoofed email
- 312 Failing email from blocked sending servers
- Google WorkspaceAllowedBusiness email2,410Passing
- MailchimpAllowedNewsletters1,180Passing
- 12 servers (198.51.100.24 and others)Blockednamed mout.webhost.example · Example Hosting (DE)312312 spoofed
Blocked after confirming your company doesn't use these servers. Their failing email is counted as spoofed.
- Server 203.0.113.7UndecidedExample Net (BR)33 failed
Publish official server details in SPF and DKIM for Gmail
List authorized servers in your DNS SPF record and publish the public key used to verify email in DKIM.
Learn more
Ask Gmail to reject spoofed email
After reviewing RUA reports (spoofing reports) for a month or two, if no official servers are missing and legitimate email has no authentication errors, set DMARC to p=reject to ask Gmail to reject spoofed email.
Learn more
Check your company's domain settings now
Enter your company domain to see its DMARC policy and whether it requests quarantine or rejection.
Frequently asked questions
More in ResourcesWhat does this check access? Will it change my email or DNS?
We read public DNS settings without sending email or changing DNS. We log the domain you enter and connection details to prevent abuse; see the privacy policy for details.
If spoofing says "Weak," will fake email reach my customers?
"Weak" means there's no request to quarantine or reject email that fails authentication. It doesn't tell you where email is delivered. Receiving services also apply their own spam filters, and DNS can't show where an email ended up.
Does DMARC cover spoofing from look-alike domains or free email accounts?
DMARC applies to email using your exact company domain. Your policy doesn’t cover look-alike domains or free email accounts such as Gmail. Report suspicious email to the email service and tell staff and customers which sending addresses you use.
What if my DMARC record already has a RUA report address?
Keep your existing RUA address and policy. Add the RUA address Genharden provides alongside it.
What can I use for free?
Try Pro for 14 days without a card. Then your workspace switches to Free at no charge: 1 domain, 1,000 DMARC-passing emails per month as counted in RUA reports, and 14 days of RUA report history. We'll email you if you exceed the email limit. If you're still over that month's limit seven days later, access is restricted to settings until the next month.
What is DMARC, and do I need it?
DMARC lets your domain ask receivers how to handle email that fails authentication. p=none requests no quarantine or rejection; p=quarantine requests quarantine, and p=reject requests rejection. Receivers decide the final handling.
What is the difference between p=none, p=quarantine and p=reject?
p=none requests no quarantine or rejection for DMARC failures. p=quarantine asks receivers to quarantine failing email, for example in spam, and p=reject asks them to refuse it. Receivers decide the final handling. Raising the policy before you are ready can also affect legitimate email.
Will p=reject block my legitimate email?
It can, if a sending server you rely on still fails authentication. That's why we show the effect on the last 30 days of email first. An allowed sending server that still fails stays on your list as a task, and we walk you through 14 days at quarantine before reject. Sending servers that send email once a quarter may not appear in 30 days, so check those yourself.
SPF and DKIM pass. Why does DMARC fail?
DMARC needs SPF or DKIM to pass with a domain that aligns with the domain in the From address. Authentication can pass while DMARC fails if neither passing domain aligns. Compare the authenticated domains with the From domain for each sending server.
Can it tell me why my emails are going to spam?
DMARC aggregate reports (RUA) show SPF, DKIM, and DMARC failures by sending server. The receiving server must confirm whether authentication caused spam filtering; RUA reports can't explain filtering caused by content or sender reputation.
Do I need to set up every service that sends my email?
Check SPF and DKIM settings for each service that sends email with your domain. We identify common services by name in RUA reports and provide setup guidance. Other servers are identified by IP and network.
I have no DMARC record yet. Can I start?
Add a domain to get the DMARC record to publish in DNS. Keep your existing policy and add the RUA address to rua, or, if you don't have DMARC yet, start with p=none and a RUA reporting address.
Who changes DNS?
On Free, Plus and Pro, you do. Genharden DMARC never touches your DNS. We show the record to publish, then read DNS again to confirm the change. Without DNS access, you get a note to hand to whoever manages it. On the Custom plan, your dedicated specialist takes this on within the agreed scope.
What does a DMARC aggregate report (RUA) contain?
DMARC aggregate reports (RUA) contain sending server IPs, email counts, and SPF, DKIM, and DMARC results for your domain. They don't contain individual email subjects, bodies, or recipient addresses.
Can I receive failure reports (RUF) too?
We provide a failure report (RUF) address alongside the RUA address in your DMARC record. RUF reports can contain authentication details and addresses or body content from the original email. Only some receivers send them; Gmail and Microsoft 365 don't. They aren't added to email counts or monthly DMARC-passing email usage.