A Complete Guide for Google Workspace MX Records in 2026

Google Workspace MX records are DNS entries that point your domain's incoming email to Google's mail servers. MX stands for Mail Exchange, and these records are the fundamental routing instructions that tell every email server on the internet "when someone sends email to @yourdomain.com, deliver it here."

Without correct MX records, email sent to your domain has nowhere to go. It bounces, it disappears, or it gets delivered to whatever default mail server your registrar set up, which probably isn't Google.

This might sound like a one-time setup task you handle and forget about. For most businesses, it is. But for anyone running cold email or B2B outreach at scale, your MX record configuration is the foundation that everything else sits on. Authentication records like SPF, DKIM, and DMARC all reference or depend on your DNS being clean. If your MX records are wrong, misconfigured, or still pointing to a previous provider, your email authentication will fail. And in 2026, failed authentication doesn't just mean a yellow warning in someone's inbox. It means permanent rejection.

Google and Yahoo tightened their sender requirements in 2024, and they've continued to enforce them more strictly every quarter since. Microsoft disabled Basic Auth for SMTP AUTH in March 2026, requiring OAuth 2.0 for all connections. The result is that dns records for email have gone from a "set it and forget it" technical checkbox to a critical piece of your outbound infrastructure.

The latest State of Cold Email report (by Hunter.io) shows Google Workspace accounts averaging a 5.9% reply rate compared to Microsoft 365 at over 4%. That performance gap makes Google Workspace the preferred sending platform for most outbound teams. But you only get that advantage if your setup is clean from the DNS level up. And that starts with MX records.

If you'd rather skip the manual configuration entirely, Smartlead's SmartSenders handles complete Google Workspace email setup as a service, including DNS configuration, authentication records, and initial warmup. But whether you do it yourself or have it done for you, understanding what these records do and why they matter will save you hours of troubleshooting down the road.

What are the correct Google Workspace MX record values?

Google publishes five MX records that you need to add to your domain's DNS settings. These google workspace mx records values are the official entries - the priority numbers determine the order in which receiving servers try each mail server. Lower priority numbers get tried first.

Note: some Google Admin setups show smtp.google.com as a simplified single MX record option. Both configurations route email to Google, but the five ASPMX records above are the standard recommendation and what the Admin console uses by default for new Workspace setups.

A few things to note about these values. The Host field should be set to @ or left blank depending on your registrar. Some registrars (like GoDaddy) want @, while others (like Cloudflare) want the field empty. Both mean "the root domain." Don't type your actual domain name in the Host field unless your registrar specifically asks for it, because that's the most common mistake and it results in records pointing to a subdomain instead of your primary domain.

The priority numbers matter. ASPMX.L.GOOGLE.COM at priority 1 is the primary server. The ALT servers are backups. If Google's primary server is temporarily unavailable (rare, but it happens), email gets routed to the alternates. You need all five records. Some guides online say you can get away with just the primary, but that creates a single point of failure that can delay email delivery during Google's maintenance windows.

One more thing: don't add a trailing period after the server names unless your registrar requires it. Some DNS providers (particularly those using BIND-style notation) expect a trailing dot. Most modern registrar interfaces do not. Check your registrar's documentation if you're unsure.

How do you set up Google Workspace MX records step by step?

Here's the complete mx record configuration process. The exact interface varies by registrar, but the steps are the same everywhere.

Step 1: Sign in to your domain registrar. This is wherever you bought your domain. Common registrars include GoDaddy, Namecheap, Cloudflare, Google Domains (now Squarespace Domains), and Route 53 if you're on AWS. If you're not sure which registrar you used, do a WHOIS lookup on your domain. It'll tell you.

Step 2: Navigate to DNS management. Look for "DNS Settings," "DNS Management," "DNS Zone," or "Name Server Management." Every registrar calls it something slightly different, but they all have it.

Step 3: Delete any existing MX records. This is critical. If your domain previously used a different email provider (or your registrar set up default MX records pointing to their own mail servers), those old records will conflict with Google's. Delete all of them. You want a clean slate before adding the Google entries.

Step 4: Add all five Google Workspace MX records. Enter each record from the table above, one at a time. Set the TTL (Time to Live) to 3600 seconds (1 hour) if your registrar gives you the option. Some registrars set this automatically and don't let you change it, which is fine.

Step 5: Save and verify. After adding all five records, save your changes. Then go to the Google Admin console (admin.google.com), navigate to Account > Domains > Manage Domains, and click "Activate Gmail." Google will check your MX records and confirm whether they're correct.

Step 6: Wait for DNS propagation. MX records can take anywhere from a few minutes to 72 hours to propagate across the internet, though most propagate within 1-4 hours. During this period, email delivery might be inconsistent. Don't panic if a test email doesn't arrive immediately. Give it at least 2 hours before troubleshooting.

Step 7: Send a test email. Once propagation is complete, send an email from an outside account (Gmail, Outlook, Yahoo) to your Google Workspace address. If it arrives in your inbox, your MX records are working.

You can verify your records are correct at any time using MXToolbox (mxtoolbox.com/MXLookup.aspx). Enter your domain and it'll show you every MX record that's currently live, along with their priorities. If you see entries that don't match Google's five servers, you've got a configuration issue.

For teams managing multiple sending domains for cold email setup, this process gets repetitive fast. If you're setting up 5, 10, or 20+ domains for outbound, Smartlead's SmartSenders does all of this for you. They handle the DNS configuration, authentication records, and initial warmup across every domain so you can focus on writing campaigns instead of navigating registrar dashboards.

What DNS records should you configure alongside MX records?

MX records get your email flowing, but they're only one piece of the google workspace email setup. In 2026, you need three additional DNS records to pass email authentication checks: SPF, DKIM, and DMARC. Without all three, your emails will be rejected by Google, Yahoo, and Microsoft. This isn't optional.

SPF (Sender Policy Framework) tells receiving mail servers which IP addresses and servers are authorized to send email on behalf of your domain. For Google Workspace, you need this TXT record:

v=spf1 include:_spf.google.com ~all

If you're also sending through Smartlead or another platform, you'll need to include their SPF record too. SPF records are additive. You combine them into a single TXT record like this:

v=spf1 include:_spf.google.com include:spf.smartlead.ai ~all

Important: you can only have ONE SPF record per domain. If you add a second TXT record starting with v=spf1, both will break. Combine all your authorized senders into a single record.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing email that proves the message wasn't altered in transit. Google Workspace generates a unique DKIM key for your domain in the Admin console. Go to Apps > Google Workspace > Gmail > Authenticate Email, and Google will give you a TXT record to add to your DNS. The record name is usually google._domainkey.yourdomain.com and the value is a long string of characters that serves as your public key.

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties SPF and DKIM together and tells receiving servers what to do when authentication fails. Start with a monitoring-only policy:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

Once you've confirmed everything passes for 2-4 weeks, tighten it to:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com

And eventually:

v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com

The p=reject policy is where you want to end up. It tells receiving servers to completely reject any email that fails authentication, which protects your domain from spoofing and signals to mailbox providers that you take email authentication seriously. Google and Yahoo now expect bulk senders to have a DMARC policy in place. Non-compliant emails get permanently rejected, not just filtered to spam.

For a deeper walkthrough on getting spf dkim dmarc right, including common pitfalls and testing methods, check out our complete email authentication guide.

How do you verify your Google Workspace MX records are working?

Verification isn't just a one-time check after setup. Your dns records for email can break silently if someone on your team edits DNS settings, if your registrar pushes an update, or if you migrate to a new hosting provider. Here's how to verify and keep verifying.

Method 1: Google Admin Console. Log into admin.google.com, go to Account > Domains > Manage Domains, and check the status next to your domain. A green checkmark means Google has verified your MX records. A yellow or red indicator means something's off.

Method 2: MXToolbox. Go to mxtoolbox.com/MXLookup.aspx, enter your domain, and confirm all five Google MX servers appear with the correct priorities. MXToolbox also flags misconfigurations, duplicate records, and records that conflict with each other.

Method 3: Command line. If you're comfortable with terminal, run dig yourdomain.com MX (macOS/Linux) or nslookup -type=mx yourdomain.com (Windows). You'll see the raw MX records exactly as the DNS servers return them.

Method 4: Smartlead's SmartDelivery. Once your Google Workspace accounts are connected to Smartlead, you can use SmartDelivery to run inbox placement tests. This goes beyond MX verification. It sends test emails and shows you exactly where they land across Gmail, Outlook, Yahoo, and other providers. If your MX records, SPF, DKIM, or DMARC have issues, you'll see it reflected in placement results before it affects real campaigns.

After any DNS change, wait at least 2 hours and then verify using at least two of these methods. DNS propagation isn't instant, and different verification tools query different DNS servers, so you might get inconsistent results during the propagation window.

What are the most common MX record mistakes and how do you fix them?

After helping thousands of users set up sending infrastructure, these are the mistakes that come up again and again. Most of them are easy to make and easy to fix once you know what to look for.

Mistake 1: Leaving old MX records in place. This is the number one cause of MX record problems. If your domain has leftover MX records from a previous email provider (or default records from your registrar), they'll compete with Google's records. Email will get split between providers unpredictably. Some messages go to Google, some go to the old provider, and you'll think emails are disappearing. The fix: delete every MX record that doesn't point to Google's servers before adding the new ones.

Mistake 2: Wrong Host field value. Entering your full domain name (like "yourdomain.com") in the Host field instead of @ or blank creates MX records for a subdomain. Email to user@yourdomain.com won't route to Google because the records are actually set for yourdomain.com.yourdomain.com (a double domain). Check your registrar's specific requirements for the Host field. When in doubt, use @.

Mistake 3: Incorrect priority numbers. Swapping the priority values (putting ALT servers at priority 1 and the primary at priority 10) won't completely break email delivery, but it will route email to backup servers first, which can introduce delivery delays. Match the priorities exactly as shown in the table above.

Mistake 4: Adding a trailing period when your registrar doesn't expect one. Some DNS providers auto-append the trailing dot. If you manually add one and the registrar also adds one, you end up with a double-dot record that's invalid. If your MX lookup shows values like ASPMX.L.GOOGLE.COM.. (two dots), that's the issue.

Mistake 5: Multiple SPF records. This isn't an MX record issue specifically, but it often happens at the same time as MX setup. If you add Google's SPF record as a new TXT entry without removing or merging the existing one, both records break. You get an SPF PermError, and your email authentication fails across all receiving servers. Always merge SPF includes into a single record.

Mistake 6: Not waiting for propagation. Checking your records 5 minutes after adding them and panicking when they're "not working" is a classic. DNS changes take time. Give it 1-4 hours minimum. If records still aren't resolving after 24 hours, then you have a genuine configuration issue.

Mistake 7: CNAME conflict. If your domain has an existing CNAME record at the root level (@), it conflicts with MX records. The DNS specification doesn't allow CNAME records to coexist with MX records at the same level. You'll need to remove the CNAME or restructure your DNS to avoid the conflict.

For teams running multiple sending domains and managing their cold email setup across a large infrastructure, these mistakes multiply fast. Getting one domain right is straightforward. Getting 20 domains right simultaneously without any typos, forgotten records, or propagation issues is where things get messy. That's exactly the scenario where SmartSenders and Smartlead's Setup as a Service saves the most time.

Why is Google Workspace the preferred choice for cold email in 2026?

If you're building google workspace for cold email infrastructure, you've probably already heard the recommendation to use Google over Microsoft. Here's why that advice holds up, and where the nuance is.

The performance gap is real. As we mentioned earlier Google Workspace accounts averaging a 5.9% reply rate, while Microsoft 365 sits at roughly 4%. That 1.9 percentage point difference might not sound like much, but at scale it compounds significantly. If you're sending 1,000 emails per day across multiple accounts, that's the difference between 59 replies and 40 replies. Over a month, it's nearly 600 additional conversations.

Google's deliverability infrastructure is also more predictable. Their sender requirements are well-documented, their Postmaster Tools give you direct visibility into how your domain is performing, and their authentication enforcement is consistent. You know exactly what the rules are and exactly how to check whether you're meeting them.

That said, the Reddit consensus among outbound professionals is clear: diversification across Google and Microsoft is table stakes in 2026. Sending exclusively from one provider puts all your eggs in one basket. If Google updates their filtering algorithm or temporarily throttles your domain, your entire operation stalls. Running a mix of Google Workspace and Microsoft 365 accounts gives you redundancy.

From a cost perspective, Google Workspace runs $7.20 per user per month on the Business Starter plan. If you're running 50 sending accounts, that's $360/month. For comparison, dedicated SMTP servers for 50 accounts typically run $50-100/month, but they don't come with built-in calendar, drive, or the trust signals that Google's infrastructure carries. The premium is worth it for most teams because Google's servers have established reputation that new SMTP servers don't.

Once your Google Workspace accounts are configured and your MX records are verified, connecting them to Smartlead takes about two minutes per account. From there, Smartlead's built-in warmup network gradually builds your sender reputation by exchanging real emails across its peer-to-peer network. New domains typically need 3-6 weeks of warmup before they're ready for full-volume outbound, and trying to skip this step is the fastest way to destroy a brand-new domain's reputation.

With unlimited contact storage and free verified prospects through SmartProspect, you're not paying extra per contact to maintain clean, verified lists. That matters because list quality is the single biggest factor in keeping your bounce rate low and your sender reputation healthy after all the DNS setup work is done.

How do you connect Google Workspace to Smartlead after MX setup?

Once your google workspace mx records are verified and your SPF, DKIM, and DMARC records are in place, you're ready to connect your accounts to a sending platform. Here's how the connection works with Smartlead.

Step 1: Enable IMAP in Google Workspace. Go to the Google Admin console, navigate to Apps > Google Workspace > Gmail > User Settings, and make sure IMAP access is enabled. Smartlead uses IMAP to track replies and manage conversations in the unified inbox.

Step 2: Set up OAuth 2.0 or an App Password. Google no longer supports basic username/password authentication for third-party apps. You'll either connect via OAuth 2.0 (the recommended method, handled directly in Smartlead's account connection flow) or generate an App Password if you have 2FA enabled and prefer that route.

Step 3: Add the account in Smartlead. In the Smartlead dashboard, go to Email Accounts, click Add Account, select Google Workspace, and follow the OAuth flow. Smartlead will verify the connection and confirm your account is ready.

Step 4: Configure sending limits. Start conservative. For a new Google Workspace account, set your daily sending limit to 20-30 emails per day during the warmup phase. Smartlead's warmup system will handle the gradual ramp-up automatically. After 3-6 weeks, you can increase to your target volume, though most teams cap individual Google Workspace accounts at 50-75 emails per day to stay safely within Google's sending limits.

Step 5: Run a deliverability test. Before launching your first real campaign, use SmartDelivery to run an inbox placement test. Send a test email from your new account and verify it's landing in the primary inbox across Gmail, Outlook, and Yahoo. If anything's off, the spam checker will help you pinpoint the issue.

Step 6: Start warmup. Enable email warmup in Smartlead for each new account. The warmup network sends and receives real emails on your behalf, building positive engagement signals that mailbox providers use to evaluate your sender reputation.

For teams setting up 10+ accounts, Smartlead's bulk account import lets you connect multiple Google Workspace accounts at once rather than adding them one at a time. Combined with SmartInfra for dedicated sending infrastructure, you get a fully isolated sending environment where each account's reputation is completely separate.

What should your complete Google Workspace DNS configuration look like?

Here's the full picture. After completing your google workspace email setup, your domain's DNS should have all of these records. Use this as a checklist.

If you're using Smartlead alongside Google Workspace, remember to add Smartlead's SPF include to your existing SPF record. The merged record looks like:

v=spf1 include:_spf.google.com include:spf.smartlead.ai ~all

Run your domain through MXToolbox, Google Admin Console verification, and a SmartDelivery inbox placement test after setting everything up. All three should come back clean before you start sending.

Frequently asked questions

How long does it take for Google Workspace MX records to propagate?

Most MX records propagate within 1-4 hours, though it can technically take up to 72 hours in rare cases. If you set your TTL to 3600 seconds (1 hour), propagation is usually on the faster end. Don't make DNS changes and immediately test. Wait at least 2 hours, verify with MXToolbox, and then send a test email from an external account.

Can I use Google Workspace MX records with a subdomain?

Yes. If you want email for a subdomain (like outreach.yourdomain.com), add the same five Google MX records but set the Host field to "outreach" instead of "@". This is actually a common pattern for cold email setup because it keeps your outbound sending separate from your primary business domain. You'll also need separate SPF, DKIM, and DMARC records for the subdomain.

What happens if I only add one MX record instead of all five?

Email will still work most of the time. The single server handles delivery when it's available. But if that server is temporarily down for maintenance, your incoming email has nowhere to go. Messages queue on the sending server and get retried, but some senders give up after a certain number of attempts. Adding all five records costs nothing and provides redundancy. There's no reason not to do it.

Do I need to change MX records if I'm only using Google Workspace for sending (not receiving)?

If you're only sending outbound email through Google Workspace and receiving email through a different provider, you don't need to change your MX records. MX records control where incoming email is delivered. Outbound sending is controlled by the server you're sending from, plus your SPF, DKIM, and DMARC records. However, most cold email setups use Google Workspace for both sending and receiving (to capture replies), so you'll typically want the full MX configuration.

How do I know if my Google Workspace MX records are causing deliverability issues?

MX record problems primarily affect incoming email, not outgoing. If you're not receiving replies to your campaigns, check your MX records first. If you're sending but emails are landing in spam, the issue is more likely with your SPF, DKIM, DMARC configuration, your sender reputation, or your content. Use SmartDelivery to isolate whether it's an authentication issue or a reputation issue.

Should I use Google Workspace or Microsoft 365 for cold email?

Both work, and most serious outbound teams use a mix of both. Google Workspace edges ahead in reply rates (5.9% vs 4%+ per Hunter.io), has better transparency through Postmaster Tools, and benefits from widespread trust. Microsoft 365 offers different IP ranges and inbox provider diversity. The consensus among experienced outbound operators: run both and distribute your sending volume across them. Check our cold email software guide for a broader comparison of tools.

Can Smartlead set up Google Workspace and MX records for me?

Yes. Smartlead's SmartSenders / Setup as a Service handles the complete process: domain purchase, Google Workspace provisioning, DNS and MX record configuration, email authentication (spf dkim dmarc), and initial warmup. It's particularly useful if you're setting up multiple domains at once and don't want to repeat the DNS process 10 or 20 times.

How do you find MX records in Google Workspace?

To see which MX records are currently live for your domain, go to your registrar's DNS management panel and look for existing MX entries. To get Google's recommended records, go to the Google Admin Console (admin.google.com), navigate to Account > Domains > Manage Domains, and click through the email setup flow. Google lists all five recommended MX records there. You can also use MXToolbox - enter your domain and it shows every active MX record with priorities in seconds.