Skip to content

Home Topics Email Authentication DMARC report analysis

Email Authentication · DMARC report analysis

DMARC aggregate reports for Google Workspace: setup and requirements

Short answer

Google Workspace weighs DMARC aggregate reports directly when deciding inbox placement. Workspace admins control SPF, DKIM, and DMARC from the Admin console, and inbound policy from the Gmail spam settings. Follow the setup steps below and verify with a test message to a Google Workspace mailbox.

Workspace admins control SPF, DKIM, and DMARC from the Admin console, and inbound policy from the Gmail spam settings.

What DMARC aggregate reports are#

DMARC aggregate (RUA) reports are daily XML files sent by mailbox providers listing, per sending IP, how many messages claimed your domain and whether they passed SPF, DKIM, and alignment. Forensic (RUF) reports contain samples of individual failures.

Why it matters#

Reports are the only way to see who is sending as your domain, including vendors you forgot and attackers you never knew about. Moving to p=reject safely depends on reading them.

Setting up DMARC aggregate reports for Google Workspace#

  1. Publish rua=mailto: pointing to a dedicated mailbox or a report processor.
  2. Collect reports for at least two weeks before drawing conclusions.
  3. Group sources by IP owner and match each to a known vendor.
  4. Fix alignment for legitimate sources; treat unknown high-volume sources as spoofing.
  5. Track pass rate weekly and tighten policy as it approaches 100%.
Fragment of an aggregate report record
<record>
  <row><source_ip>203.0.113.10</source_ip><count>412</count>
    <policy_evaluated><disposition>none</disposition><dkim>pass</dkim><spf>fail</spf></policy_evaluated></row>
  <identifiers><header_from>example.com</header_from></identifiers>
</record>

How Google Workspace reports results#

Open a delivered test message in Google Workspace and view the original or headers. Look for Authentication-Results and any provider-specific verdict headers. Use the provider's sender dashboard for aggregate reputation.

Common mistakes#

  • Reading raw XML by hand and giving up after day two.
  • Ignoring low-volume unknown sources that turn out to be your own systems.
  • Expecting RUF reports; most large providers no longer send them.

Frequently asked questions#

How do I read a DMARC report?

Each record lists a source IP, message count, SPF and DKIM results, and alignment. Use an analyzer to aggregate by source; the goal is to name every IP range.

Why do I see mail from IPs I do not recognize?

Common causes are forwarding, a vendor you forgot, an employee's personal tool, or spoofing. Volume and geography usually tell them apart.

Does Google Workspace require DMARC aggregate reports?

Workspace admins control SPF, DKIM, and DMARC from the Admin console, and inbound policy from the Gmail spam settings. Treat DMARC aggregate reports as required for any meaningful volume.

Analyse your own setup

All analysers
Technical analysis

DMARC record analyser

Grade a DMARC record on enforcement, not just syntax.

Runs in your browser

Keep reading on DMARC report analysis