What does Google Postmaster Tools show, and how does it relate to DMARC?
Google Postmaster Tools is a free Gmail dashboard that shows how Gmail sees mail from your domain: user-reported spam rate, SPF, DKIM and DMARC pass rates, delivery errors and a compliance status check against Google's sender guidelines. It only covers mail delivered to Gmail. DMARC aggregate reports cover every participating receiver and every IP that sends as your domain.
This guide explains what each Postmaster Tools dashboard measures, how to add and verify a domain, why low-volume domains show no data, and how to read the authentication and compliance dashboards. It then compares Postmaster Tools with DMARC (Domain-based Message Authentication, Reporting and Conformance) aggregate reports, and sets out a workflow for an MSP (managed service provider) running many client domains. For protocol background, start with the DMARC guide.
Key takeaways
- Postmaster Tools reports on Gmail traffic only. It tells you how Gmail rates your mail, not who is sending it.
- DMARC aggregate reports, defined in RFC 9990, list each source IP, message count and SPF and DKIM result from every receiver that reports, including Gmail.
- Google's sender guidelines ask you to keep the spam rate in Postmaster Tools below 0.10% and never reach 0.30%.
- Low-volume domains often show empty dashboards, because Google omits data on low-volume days to protect user privacy.
- When Postmaster Tools shows authentication failures, DMARC aggregate reports are where you find the source that is failing.
What dashboards does Postmaster Tools have today?
Google's Postmaster Tools dashboards help page lists eight dashboards: Compliance status, Spam rate, IP reputation, Domain reputation, Feedback loop, Authentication, Encryption and Delivery errors. You pick a verified domain, a dashboard and a time range of 7, 30, 60, 90 or 120 days. Data is usually updated within 24 hours, and all times are in UTC.
Google has rebuilt the tool as Postmaster Tools v2. Its deprecation notice for the old interface says v2 keeps all v1 functionality except Domain and IP reputation, which will be retired and replaced by a new reputation dashboard. It adds a Compliance dashboard and API endpoints for compliance status, domain management and batch queries. When we checked in November 2026, Google said the retirement of the old web interface had been postponed and gave no date. Web users are redirected to v2 automatically. Developers using the v1 API must move to the v2 API, which adds a domains.getComplianceStatus method.
Because the reputation dashboards are on their way out, do not build a client reporting process around them. The spam rate, authentication, compliance and delivery error dashboards carry over.
| Dashboard | What it measures | Useful for |
|---|---|---|
| Compliance status | Checks against Google's sender guidelines, each marked Compliant, Needs work or No data found | Bulk sender readiness |
| Spam rate | Share of DKIM-authenticated inbox mail that users marked as spam | Complaint trends |
| Authentication | Percentage of mail passing SPF, DKIM and DMARC for your From domain | Spotting authentication gaps at Gmail |
| Delivery errors | Percentage of authenticated mail rejected or temporarily failed, with reasons | Diagnosing Gmail bounces |
| Encryption | Share of mail sent and received over TLS | TLS compliance |
| Feedback loop | Spam rates per campaign identifier | High-volume senders with FBL headers |
| IP and Domain reputation | Bad, Low, Medium or High rating | Being retired in v2 |
How do you set up Google Postmaster Tools for a domain?
Sign in at postmaster.google.com with a Google account, add the domain, then prove you own it with a DNS record. Google's Set up Postmaster Tools page describes three steps: add the domain on the Manage Domains page, verify it with the TXT or CNAME record Google gives you, then optionally add other users.
- Open Manage Domains and click Add new domain.
- Enter the domain and click Create.
- Choose More options, then Verify domain, and copy the TXT record.
- Publish the TXT record at your DNS host and click Verify.
Verification usually completes quickly but can take up to 10 minutes to update. Dashboards show nothing until the domain is verified. Check the record has propagated before you click Verify:
dig +short TXT example.com
"v=spf1 include:_spf.google.com ~all"
"<verification string copied from Postmaster Tools>"
On Windows, the equivalent is:
Resolve-DnsName -Name example.com -Type TXT | Select-Object -ExpandProperty Strings
If you set up more than one Google account for the same domain, each account needs its own verification record. That matters for MSPs, covered below.
Which domain should you add: the organisational domain or a subdomain?
Add the domain that authenticates the mail. Google says to enter the DKIM d= domain or the SPF (Return-Path) domain. For most clients that is the organisational domain, such as example.com. If a marketing platform signs as news.example.com, add that subdomain separately after the parent. Once the parent is verified, its subdomains need no separate verification.
The Compliance status dashboard reports on primary domains only, although subdomain traffic feeds into its results. So add the organisational domain first in every case, then the sending subdomains you want separate charts for. DMARC for subdomains explains how those subdomains inherit policy.
Why does Postmaster Tools show no data for a domain?
Usually because the domain sends too little mail to Gmail. Google says that to protect the privacy of Gmail users, dashboards might not include all data on days when volume is low, and the compliance checks show "No data found" when too few emails meet the criteria. Google publishes no minimum number, so treat empty charts as normal for small senders.
Other causes are worth ruling out:
- The domain is added but not verified.
- You added a domain that never appears as the DKIM
d=or SPF domain, so no traffic matches it. - The client's mail is mostly internal, or goes to recipients outside Gmail.
- Data has not arrived yet: compliance status uses a rolling average, so changes can take up to seven days to show.
This is the first big gap for MSPs. A typical small business client sends a few dozen messages a day to Gmail users and may never get a chart. DMARC aggregate reports have no privacy threshold of that kind: Gmail, Microsoft and other receivers send a report for each domain they saw traffic for during the reporting period, even a handful of messages.
How do you read the authentication dashboard?
The authentication dashboard shows the percentage of mail with your domain in the From header that passed SPF, DKIM and DMARC at Gmail. Google says correctly configured DKIM and DMARC typically reach 95% or higher, while SPF is often lower because third-party senders and forwarding break it. A falling DMARC line is the signal to act.
A second view groups results by DKIM and SPF domain, but it does not show DMARC. Use it to see whether a platform is signing with its own domain instead of the client's.
What the dashboard cannot tell you is which sender caused the failures. It gives percentages, not source IPs or platforms. A drop from 99% to 92% DMARC pass could be a new CRM, a misconfigured on-premises scanner, forwarding, or a spoofing campaign. Only the aggregate reports separate those.
How do you read the compliance status dashboard?
The compliance status dashboard checks your domain against Google's email sender guidelines and marks each requirement Compliant, Needs work or No data found. All senders get checks for SPF and DKIM, DNS records, message formatting, encryption and user-reported spam rate. Bulk senders get extra checks.
Google defines a bulk sender here as one that sends about 5,000 or more messages to Gmail accounts in 24 hours. Those senders are also checked for DMARC authentication, one-click unsubscribe and honouring unsubscribe requests. The guidelines accept a DMARC policy of p=none, so a domain can pass the DMARC check while still unprotected against spoofing. The full requirement set, and why it pushes businesses towards DMARC, is covered in Google and Yahoo sender requirements and the wider Google, Yahoo and Microsoft comparison.
A minimal record that satisfies the DMARC check and starts reporting looks like this:
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
What spam rate does Google want?
Below 0.10%, and never 0.30% or higher. Google's sender guidelines say to keep spam rates reported in Postmaster Tools below 0.10% and to avoid ever reaching 0.30%. The 0.3% figure is the hard limit in the requirements for all senders. The spam rate dashboard is the only official place you can see this number.
The rate only counts DKIM-authenticated mail that reached the inbox and was then marked as spam. Google notes that if Gmail already filters a lot of your mail to spam, the rate can look artificially low. A low spam rate alongside rising delivery errors is a warning, not a pass.
Postmaster Tools or DMARC reports: which answers your question?
Use Postmaster Tools for how Gmail judges your mail, and DMARC aggregate reports for who is sending as your domain and how every receiver treats it. RFC 9990 reports list each source_ip, message count, disposition and DKIM and SPF results. Postmaster Tools gives Gmail-wide percentages without sources.
| Question you have | Best source | Why |
|---|---|---|
| Is Gmail users' spam complaint rate above 0.3%? | Postmaster Tools | Only Google publishes this figure |
| Does the domain meet Gmail's bulk sender checks? | Postmaster Tools | Compliance status dashboard |
| Why is Gmail rejecting or deferring our mail? | Postmaster Tools, then bounce logs | Delivery errors lists reasons |
| Which IPs and platforms send mail as this domain? | DMARC reports | source_ip per record |
| Is someone spoofing the domain? | DMARC reports | Unknown sources failing alignment |
| Does Microsoft or Yahoo see the same failures? | DMARC reports | Reports come from many receivers |
| Which sender broke DKIM after a change? | DMARC reports | DKIM domain and selector per source |
Is it safe to move to p=quarantine or p=reject? |
DMARC reports | Shows every legitimate source first |
| Do we have any data for a tiny client domain? | DMARC reports | No low-volume privacy threshold |
The two overlap on one point: both show Gmail's view of DMARC pass and fail. If the Postmaster Tools DMARC pass rate and the Gmail rows in your aggregate reports disagree, check the time window first. Postmaster Tools uses daily UTC data and rolling averages, while each aggregate report covers its own period, typically one UTC day. DMARC aggregate reports explained walks through the XML.
What should you do when Postmaster Tools shows authentication failures?
Go to the DMARC aggregate reports for the same dates and filter for Gmail as the reporter. Find the source IPs where SPF or DKIM failed or did not align, identify the platform behind each one, then fix that platform's DKIM signing or SPF include. Postmaster Tools confirms the fix when the pass rate recovers.
A practical sequence:
- Note the dates and which check fell (SPF, DKIM or DMARC) in the authentication dashboard.
- Open the aggregate reports for those dates and look for records where
policy_evaluatedshowsdkimandspfboth asfail. - Group the failing records by
source_ipand look up each IP's owner. - Sort sources into legitimate senders, forwarders and unknown senders.
- Fix legitimate senders: enable custom DKIM on the platform, or align the Return-Path with a custom bounce domain. See DMARC alignment explained.
- Leave forwarding failures alone if DKIM survives elsewhere; forwarded mail often breaks SPF only.
- Treat unknown sources failing both checks as possible spoofing, which
p=quarantineorp=rejectwill stop.
A failing record in an aggregate report looks like this:
<record>
<row>
<source_ip>203.0.113.25</source_ip>
<count>412</count>
<policy_evaluated>
<disposition>none</disposition>
<dkim>fail</dkim>
<spf>fail</spf>
</policy_evaluated>
</row>
<identifiers>
<header_from>example.com</header_from>
</identifiers>
<auth_results>
<dkim><domain>crm-vendor.example</domain><selector>s1</selector><result>pass</result></dkim>
<spf><domain>bounce.crm-vendor.example</domain><result>pass</result></spf>
</auth_results>
</record>
Here DKIM and SPF both pass, but for the vendor's domains, not example.com, so DMARC fails on alignment. Postmaster Tools would show only a lower DMARC percentage. If the bounces carry a code such as 550 5.7.26, Gmail 550 5.7.26 and authentication bounce codes explains what each one means.
How should an MSP run Postmaster Tools across many client domains?
Verify each client domain in a Google account the MSP controls, add named technicians as users, and use DMARC aggregate reports as the daily monitoring layer. Postmaster Tools has no multi-tenant view in its web interface: you switch domains one at a time. Keep it for Gmail-specific questions on clients that send meaningful volume to Gmail.
Things to plan for:
- Account ownership. Use a dedicated MSP Google account per team rather than a technician's personal login, so access survives staff changes.
- Adding users. Google lets you add users only to verified domains, via Manage users. Each person needs a Google or Google Workspace account, and Google does not notify them, so tell them yourself.
- Client-owned accounts. If the client already verified the domain, ask them to add your MSP account as a user. A separate MSP account needs its own verification record.
- Volume triage. Many small clients will show "No data found". Record that in the client file so nobody chases empty dashboards.
- API at scale. The v2 API supports batch queries across domains, useful if you pull Gmail statistics into your own reporting.
- Offboarding. Remove ex-staff and departing clients' domains from the account.
DMARC aggregate reports cover what Postmaster Tools cannot: every client domain, every receiver, every source. DMARC AI processes aggregate (RUA) reports with AI source classification, so technicians see which platforms send for each client. It does not connect to Postmaster Tools, so the two stay separate checks. For multi-client operations, see multi-tenant DMARC management and DMARC for MSPs.
Does DMARCbis change any of this?
Not the division of labour. RFC 9989 replaces RFC 7489 as the DMARC core standard and RFC 9990 now defines aggregate reporting. DMARCbis removes the pct tag, so rollout runs p=none, then p=quarantine, then p=reject, optionally with t=y while testing. Google's guidelines still accept p=none, so moving to enforcement remains your decision, made from aggregate report data.
FAQ
Is Google Postmaster Tools free?
Yes. Postmaster Tools is free for anyone with a Google account who can add a TXT or CNAME record to the domain's DNS. The limits are about scope rather than cost: it only reports Gmail traffic, and low-volume domains may show little or no data because Google omits data on low-volume days.
Does Postmaster Tools replace DMARC reports?
No. Postmaster Tools shows Gmail's view as percentages, without source IPs, and only for Gmail recipients. DMARC aggregate reports come from Gmail and other receivers, and list each sending IP with its SPF and DKIM results. You need the reports to find a failing sender or to plan a move to p=reject safely.
Why is my Postmaster Tools spam rate zero?
Often because volume is too low for Google to show data, or because few users mark your mail as spam. The rate only counts DKIM-authenticated mail that reached the inbox. If Gmail is already filtering much of your mail to spam, the rate can look artificially low, so check delivery errors and inbox placement too.
Can an MSP see all client domains in one Postmaster Tools account?
Yes, one Google account can hold many verified domains, but the web interface shows one domain at a time. Each domain needs DNS verification, and other people are added per domain through Manage users. For a combined view across clients, use the v2 API or a DMARC platform built on aggregate reports.
Final thoughts
Postmaster Tools answers one narrow question well: how Gmail judges a client's mail, including the spam rate Google's guidelines limit to 0.3%. It does not tell you who sends as the domain, what other receivers see, or anything useful for most small clients. Pair it with DMARC aggregate reports, which show every source and every reporting receiver, and use the reports to decide when each client is ready for enforcement.