Complete Guide on How to Set Up DMARC in Google Workspace
Guidance on how to setup DMARC in Google Workspace (New Email Send Requirements in 2024). Protect your business from spoofing by setting up DMARC in Google Workspace.
- Beginning in February 2024, senders with over 5,000 daily emails to Google and Yahoo! accounts will have to implement an active DMARC policy. Implementing the DMARC email authentication protocol in Google Workspace can safeguard your brand.
- Senders will also need to set SPF and DKIM records per domain and ensure alignment, as well as use ARC authentication for forwarded messages.
- DMARC policies can be set to reject, quarantine or simply deliver email messages that fail authentication; policies can be set separately for all your organization’s domain names.
- Reports provide feedback on the use — and potential abuse — of your domains.
New Email Send Requirements in 2024
Google and Yahoo! are changing the rules that apply to senders with over 5,000 daily emails going to Google and Yahoo! accounts. Beginning in February 2024, senders will need to implement an active DMARC policy. This news comes on the heels of a major change to PCI DSS standards which now require companies handling credit card data to use DMARC email authentication.
In addition, senders hoping to continue to reach over 5,000 Google and Yahoo! email inboxes daily will be required to set SPF and DKIM records per domain and use ARC authentication for forwarded messages.
Emails that fail authentication will be rejected or marked as spam, compromising email delivery for customer communications sent by organizations that do not meet Google’s and Yahoo!’s new rules.
Get Help from Mimecast
Mimecast can assist organizations that may have trouble meeting these new standards. A SaaS solution, Mimecast’s DMARC Analyzer empowers customers to easily manage complex deployment projects and provides 360° visibility and governance. It provides fast and simple enforcement using intuitive self-service tools, including integrated project management, delivering low risk enforcement. Explore the DMARC resource kit to learn more.
Staying Secure, Remaining Compliant
We’re all familiar with phishing schemes that entice users to enter their passwords, credit card numbers or other sensitive information, which is then stolen for nefarious purposes. The vehicle for these schemes is usually an email message that spoofs the sender’s domain.
If that spoofed domain comes from your brand, it puts your supply chain—and your reputation—at risk. And if multiple recipients report the message as spam, legitimate messages sent from your organization may land in recipients’ spam folders.
This kind of brand impersonation continues to grow. In Mimecast’s State of Email Security (SOES) research, just 29% of companies surveyed would be completely prepared if their business experienced an email-based attack that directly spoofed their email domains – down from 33% in the previous year.
If your organization uses Google Workspace for Gmail and other services, you can use the DMARC protocol in partnership with DNS servers and receiving email servers to prevent the spoofing of your brand’s domains.
What Is a DMARC Record?
A Domain-based Message Authentication, Reporting and Conformance (DMARC) record spells out for a receiving email server what to do if a Gmail message from your brand’s domain fails authentication.
DMARC works with two email authentication methods: Sender Policy Framework (SPF) and Domain Keys Identified Mail (DKIM). SPF allows you to specify which IP addresses in your domain are authorized to send email. DKIM adds a digital signature to outgoing messages. The receiving server uses SPF to authenticate the message as coming from a trusted source and DKIM to verify the message has not been altered en route.
Google Workspace DMARC Policies
A DMARC record needs to specify a policy for the action the receiving server should take if the incoming email fails SPF or DKIM authentication. There are three Gmail DMARC policy options:
- None: Deliver the message normally.
- Quarantine: Send the message to the recipient’s spam folder or to quarantine, if a quarantine option is configured.
- Reject: Do not deliver the message. Often the receiving server will inform the sender of the message failure.
Google Workspace recommends using the “none” setting at first, and then carefully reviewing the reports. Then, as you identify illegitimate versus legitimate users of your domain—marketing partners, for example, that send email on your behalf—Google suggests changing the policy to quarantine, then finally to reject. Regardless of the action taken, you can set the DMARC record to request the receiving email server send a report indicating which of your domain’s email servers are sending email and the percentage of messages passing or failing authentication.
Optionally, a second policy called alignment can be set for SPF and DKIM. The possible values are “strict” or “relaxed” and have slightly different effects for SPF and DKIM.
For SPF, the options are:
- strict: The message “from” address must exactly match the sender’s domain name.
- relaxed: Partial matches, including subdomain names, are acceptable.
For DKIM, the options are:
- strict: The domain name must exactly match the d=domainname field in the DKIM header.
- relaxed: Partial matches, including subdomains, are acceptable.
Steps to Set Up a Google Workspace DMARC Record[i]
DMARC is set up as a DNS TXT record on your domain host. The record contains flags specifying parameters for the receiving server. Each parameter is a tag-value pair. For example, to set the policy to reject, the tag-value pair would be “p=reject.”
Following these steps will get your DMARC record set up and published:
1. Configure both SPF and DKIM, then allow 48 hours before publishing the DMARC record.
2. Create the DMARC record as a line of text with tag-value pairs separated by semicolons. The accompanying table lists sample tags and possible values. Be aware that these tags and values might vary from host to host. The v and p tags are required and must be first. The remaining tags are optional.
|v||Version. This must be DMARC1.|
|p||Policy for messages that fail authentication. Possible values are reject, quarantine or none.|
|sp||Policy for subdomains. Possible values are reject, quarantine or none. The default is to apply the same policy as the domain.|
|pct||The percentage of invalid messages that should be acted on. Value must be 1-100, with 100 as the default.|
|aspf||The alignment policy for SPF. Can be s (strict) or r (relaxed). Relaxed is the default.|
|adkim||The alignment policy for DKIM. Can be s (strict) or r (relaxed). Relaxed is the default.|
|rua||The email address (preceded by mailto:) to which DMARC reports should be sent.|
3. From the management console of your domain host, locate the place where you can update the DNS record. Enter the name of your DMARC TXT record as “dmarc” followed by a period and your domain name. Some hosts will automatically append the domain name. Upload the record and save the changes.
Repeat this process for each of your domains.
Third-Party Solutions for DMARC Setup
If the Google Workspace DMARC process seems a little daunting, the good news is that security service providers like Mimecast offer cloud-based DMARC tools. Such tools simplify DMARC implementation - for example, by providing setup wizards for creating DMARC records for all your domains. Other tools validate DMARC records and create user-friendly reports and charts for analyzing messages that failed authentication, as well as forensic reports for finding the source of malicious email messages.
The Bottom Line to Setting Up DMARC in Google Workspace
As online brand impersonation continues to grow, sites like Google and Yahoo! will implement stricter standards for senders, especially those that send thousands of emails per day. Mimecast stands ready to help with DMARC Analyzer and the expertise needed to meet new DMARC guidelines.
Explore the DMARC resource kit to learn more about how you can comply with critical DMARC and Google Workspace regulation starting in February 2024.
Subscribe to Cyber Resilience Insights for more articles like these
Get all the latest news and cybersecurity industry analysis delivered right to your inbox
Sign up successful
Thank you for signing up to receive updates from our blog
We will be in touch!