What is Google Postmaster Tools V2 and how do I access it?
Updated on 5 Oct 2026: We clarified V2 access, sender compliance checks, and how to use Deliverability analysis.
Google Postmaster Tools V2 is the newer web interface for monitoring mail sent to personal @gmail.com and @googlemail.com accounts. It includes the Compliance status dashboard and operational dashboards for spam rate, authentication, feedback loop, encryption, and delivery errors. It complements DMARC reporting and message-level authentication checks.
To access it, sign in through Postmaster Tools, add the domain used for DKIM or SPF authentication, verify it in DNS, then select the dashboard you need. Google plans to redirect users to V2 automatically, and the direct Compliance status path is postmaster.google.com/v2/sender_compliance.
- Direct answer: V2 is Google's current Postmaster Tools interface, including its sender compliance dashboard.
- Access path: Use a Google account with domain access, verify the sending domain, then open V2.
- Data scope: It covers mail sent to personal Gmail and googlemail.com accounts.
- Main caveat: Compliance status reports at the primary-domain level, even when subdomains are added.
What Google Postmaster Tools V2 monitors
V2 puts sender compliance beside Gmail performance data. The Compliance status dashboard shows whether a domain meets requirements for authentication, DNS, message formatting, encryption, user-reported spam, and unsubscribe handling. Its states are Compliant, Needs work, and No data found.
The other dashboards provide the context needed to investigate a compliance warning. The Postmaster tracking guide explains those metrics in more detail. V2 shows Gmail's sender-requirement assessment, but it does not prove inbox placement.
Google Postmaster Tools V2 Compliance status dashboard showing Gmail sender requirement checks.
How V2 differs from the legacy interface
Google launched the V2 web interface in 2024 and plans to retire the legacy V1 interface. Google has postponed that retirement and has not published a replacement date. Senders can move to V2 now, while the legacy interface remains available during the transition. Google's transition notice confirms that the retirement is postponed.
Google says the operational dashboards from the legacy interface are available in V2, except for the Domain reputation and IP reputation dashboards. Those legacy reputation views are excluded from V2 and are planned for retirement. Google has announced replacement dashboards, without a launch date. Reputation labels should not be the only evidence used to diagnose delivery.
|
|
|
|---|---|---|
Interface | Older web interface | Newer interface with sender compliance checks |
Compliance | No dedicated checklist | Compliance status dashboard |
Operational data | Separate dashboard views | Spam, authentication, feedback loop, encryption, and delivery errors |
Reputation | Domain and IP dashboards | Legacy Domain and IP reputation dashboards excluded |
Access | Available during postponed transition | Automatic redirection is planned |
Current differences between the legacy interface and Postmaster Tools V2.
How to access Google Postmaster Tools V2
The access flow is simple, but the domain choice matters. Google says to add either the DKIM signing domain shown by d= or the SPF Return-Path domain. If both use the same domain, Postmaster Tools can use messages authenticated by SPF, DKIM, or both. Add and verify the primary domain first, then add key subdomains when separate non-compliance dashboard views are needed. Subdomains still need to be added, but they do not need separate DNS verification after the primary domain is verified.
- Sign in: Use a Google or Google Workspace account with verified domain access or access granted by its owner.
- Add the domain: On Manage Domains, click Add new domain, enter the DKIM signing or SPF Return-Path domain, and click Create.
- Verify DNS: Open Verify domain, publish the TXT or CNAME record Google provides in DNS, then return and click Verify.
- Open V2: Select a dashboard after verification or open the direct Compliance status path.
- Share access: For a verified domain, open More options > Manage users > New user and enter the teammate's Google account email. Tell them access is ready because Google does not send a notification.
Direct V2 path
https://postmaster.google.com/v2/sender_compliance
Access checklist
If verification fails, check the DNS host and exact TXT or CNAME value. Verification usually happens immediately, but Google says the status can take up to 10 minutes to update. Google's setup steps cover the base access process.
If access is denied, sign in with the account used for verification or have the verified owner add that account through Manage users.
- Use the right domain: Add the domain that authenticates real outbound mail.
- Allow for data lag: Data typically updates within 24 hours but can take longer; a corrected compliance state can take up to seven days.
- Check volume: Low Gmail volume can produce missing data because Google protects recipient privacy.
- Read dates in UTC: Postmaster Tools uses Coordinated Universal Time for dashboard reporting.
What the compliance dashboard checks
The V2 Compliance status dashboard separates requirements for all senders from those for bulk senders. Google defines a bulk sender as a primary domain that sends about 5,000 messages or more to personal Gmail accounts in 24 hours. Messages from subdomains count toward that primary-domain total, and bulk-sender status does not expire after a domain qualifies. Google's sender guidelines FAQ explains the domain-level threshold and permanent bulk-sender classification.
All senders
- Authentication: At least SPF or DKIM must authenticate outbound mail.
- DNS: Sending IP addresses need a PTR record whose hostname resolves back to the same IP through an A or AAAA record.
- Format: Messages need to follow RFC 5322 formatting.
- Encryption: Gmail requires TLS for mail transport.
- Spam rate: User-reported spam must remain below 0.3%; Google's recommended operating target is below 0.1%.
Bulk senders
- Authentication: SPF and DKIM are both required for the sending domain.
- DMARC: The visible From domain needs a DMARC record with at least p=none, and SPF or DKIM must pass using a domain that matches it under DMARC rules.
- One-click: Marketing and subscribed mail needs RFC 8058 one-click unsubscribe using List-Unsubscribe and List-Unsubscribe-Post headers, plus a visible unsubscribe link in the message body.
- Honor requests: Unsubscribe requests need to be processed within 48 hours.
Gmail user-reported spam-rate thresholds
Google recommends staying below 0.10% and avoiding 0.30% or higher. These are user-reported spam rates, not inbox-placement percentages.
Target range
Under 0.10%
Keep user-reported spam below Google's recommended target.
Watch closely
0.10% to below 0.30%
Review campaigns, acquisition sources, and unsubscribe handling.
Fix now
0.30% or higher
Reduce or pause risky mail until the cause is addressed.
The Spam rate dashboard measures user reports on DKIM-authenticated mail delivered to engaged recipients' inboxes. A low rate can accompany poor inbox placement if Gmail automatically filters much of the mail into spam.
A green compliance state does not prove that every message reaches the inbox. Compliance is required, but Gmail also considers recipient response and delivery signals. When complaints or delivery errors rise, inspect the affected mail stream, authentication path, list source, unsubscribe flow, and recent sending changes. Google's email sender guidelines describe the authentication and unsubscribe requirements.
How to use Deliverability analysis
Open Deliverability analysis under Compliance status for Google's recommendations about the primary domain. It adds diagnostic guidance to the checklist and helps you choose the next investigation.
- Low volume: Check the selected authentication domain and eligible Gmail traffic before assuming a blank chart indicates a sending failure.
- Delivery failures: Compare the recommendation with SMTP responses and the Delivery errors dashboard.
- Spam or recipient feedback: Review the affected campaign and opt-in records before changing sending volume.
- Sender requirements: Correct the specific authentication or unsubscribe issue, then allow for reporting lag.
Use Google's dashboard documentation to interpret these recommendations alongside message headers and DMARC evidence.
Why V2 shows Needs work or No data found
The Compliance status dashboard can look inaccurate when subdomain-level precision is expected. Google reports compliance for the primary domain and uses traffic from its subdomains to calculate that status. Adding email.example.com can provide independent data in other dashboards, but its Compliance status can still describe example.com. One subdomain with broken authentication can therefore affect the primary-domain result.
Do not debug V2 in isolation
When V2 shows Needs work, compare the finding with live DNS, real message headers, and DMARC aggregate data before changing a record. This check reduces the risk that a fix for one sender breaks another sender on the same primary domain.
- Primary domain: Compliance status combines subdomain behavior under the parent domain.
- Rolling data: A corrected issue can remain visible until Google's averages update.
- Low volume: No data found can mean that Gmail lacks enough qualifying traffic.
- Observed configuration: A DNS verdict can describe settings seen when Gmail received the evaluated messages.
- Different datasets: The compliance view can disagree with other Postmaster dashboards.
Check your DNS configuration with Suped's domain health checker, then review the relevant SPF, DKIM, and DMARC records. Use DMARC reports and real message headers to identify the sending source behind an authentication warning.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Example DMARC TXT value for _dmarc.example.com
v=DMARC1; p=none; rua=mailto:dmarc@example.com
How to connect V2 with DMARC evidence
Postmaster Tools shows how Gmail judges the domain. DMARC reports show which sources send as that domain, whether SPF or DKIM passes, and whether the authenticated domain matches the visible From domain. V2 identifies the requirement, while DMARC aggregate data helps identify the sending IP, authentication path, and affected volume. Check real message headers for the DKIM selector when it is missing from aggregate reports.
Issue steps to fix dialog showing the issue overview, tailored fix steps, and verification action
Suped's DMARC monitoring turns aggregate reports into source-level issues with fix steps. Use those reports to identify the sending IP and authentication failure behind a V2 warning, then inspect a real message before changing DNS.
When Gmail delivery looks wrong even though V2 is green, send a real message and inspect it with Suped's email tester. Review Suped's blocklist (blacklist) monitoring when delivery errors point to the sending domain or IP.
How the Postmaster Tools V2 API differs
The Google Postmaster Tools API V2 is available and is separate from the V2 browser interface. The browser remains the normal access path for manual review. The API is for automated reporting, date-range queries, multi-domain checks, compliance retrieval, and domain administration. Existing API V1 integrations need updated clients and resource calls to use V2. API access also requires OAuth authorization and permission to access the requested domain.
Current API version
v2
API V2 replaces trafficStats with domainStats. The domains.domainStats.query method retrieves statistics for a date range, domainStats.batchQuery handles multiple domains, and domains.getComplianceStatus returns SPF, DKIM, DMARC, and deliverability verdicts. Google's V2 migration guide lists the client and schema changes.
Key V2 resource changes
trafficStats -> domainStats domains.domainStats.query domainStats.batchQuery domains.getComplianceStatus
Google's API response reference also documents subdomainComplianceData when data is available for the requested subdomain. This is separate from the browser dashboard's primary-domain status.
How to investigate a V2 compliance warning
Open V2, verify the sending domain, and record a baseline for each active Gmail-facing mail stream. Check the Compliance status dashboard before a sender change and after campaigns with unusual complaint or delivery-error patterns. Keep the expected reporting lag in mind when comparing a fix with the next status.
If V2 says Needs work, identify which sender, selector, IP, Return-Path, unsubscribe flow, or DNS record caused the result. Confirm the cause with message headers and DMARC aggregate data, make the narrowest safe change, then watch both compliance and delivery metrics while Google's rolling data updates.
- Record the primary domain and each sending subdomain used by production mail.
- Capture the requirement status before changing authentication or unsubscribe settings.
- Match each warning to a real mail stream before editing DNS.
- Recheck operational dashboards after about 24 hours, allowing for longer reporting delays, and check compliance again after seven days.
