Your SPF passes. Your DKIM passes. Your DMARC passes. And your emails are still landing in spam. Nine times out of ten, the culprit nobody checks is MX record mismatch — the silent deliverability killer that sits between a correctly authenticated inbox and actual primary folder placement on Google Workspace.
What MX Mismatch Actually Does to Your Sends
MX records tell receiving mail servers where to deliver incoming mail. For cold email, they also signal legitimacy. When your sending domain's MX records don't match what Google Workspace expects — or point to a different mail host entirely — recipient servers flag the inconsistency as a trust signal failure.
It doesn't bounce. It doesn't error. It just slides into spam. And because your warmup tool shows green across the board, you never connect the dots.
🚩 The Mismatch Most People Miss
If your domain's MX records still point to your old registrar's default mail handling — or a previous email provider — while you're sending from Google Workspace, that mismatch is visible to every receiving mail server. It's one of the fastest ways to trigger spam folder placement even on a fully warmed inbox.
In our testing at Litemail, we've seen this exact scenario tank deliverability on otherwise clean accounts. The domain reputation shows Good in Google Postmaster Tools. The inbox placement in seed testing shows 94%. But live campaigns come back at 40% open rate instead of the expected 55–60%. MX mismatch every time.
The Correct Google Workspace MX Records for Cold Email Domains
These are the five MX records every Google Workspace cold email domain needs, in priority order. If any of these are missing or wrong, fix them before sending a single campaign email.
Priority | Mail Server | Required |
|---|---|---|
1 | ASPMX.L.GOOGLE.COM | ✓ Mandatory |
5 | ALT1.ASPMX.L.GOOGLE.COM | ✓ Mandatory |
5 | ALT2.ASPMX.L.GOOGLE.COM | ✓ Mandatory |
10 | ALT3.ASPMX.L.GOOGLE.COM | ✓ Mandatory |
10 | ALT4.ASPMX.L.GOOGLE.COM | ✓ Mandatory |
All five must be present with the exact priorities shown above. A common mistake is using only the first MX record and skipping the alternates. That works for basic mail delivery — but receiving servers that check for full MX configuration consistency will score your domain lower on trust signals.
💡 Check MX Records in 60 Seconds
Go to mxtoolbox.com, enter your sending domain, and run an MX lookup. You should see all five Google mail servers listed with correct priorities. If you see anything else — a registrar mail server, a Cloudflare mail handler, or a previous provider — that's your problem.
Why MX Matching Affects Sender Reputation (Not Just Delivery)
Here's the part most guides skip. MX matching isn't just about whether mail gets delivered to you — it's about what receiving servers infer about your domain's legitimacy as a sender.
Gmail's filtering algorithm cross-references multiple signals. One of those signals is whether the sending domain has a consistent, legitimate mail infrastructure — incoming and outgoing. A domain that sends from Google Workspace but has no functioning incoming mail setup looks like a throwaway domain. And throwaway domains get treated accordingly.
A SaaS founder we worked with was running outbound for a product launch — 8 inboxes across 4 domains, all on Litemail pre-warmed infrastructure. Three of the four domains had correct MX records. The fourth had been set up by a contractor who'd used Cloudflare's mail routing without finishing the Google Workspace MX migration. That one domain had a 31% lower primary inbox placement rate across 6,000 sends. Same copy, same list segment, same sending volume. MX mismatch was the only variable.
✅ The Fix: Full Infrastructure Consistency
Receiving servers want to see that your domain is a real business domain — not a burner. Real domains have consistent MX records, SPF that matches your sending provider, DKIM signatures that verify, and DMARC policies that enforce. When all four align with Google Workspace, you're signalling legitimacy at every check point.
Step-by-Step: Verify MX Records Before Every Campaign Launch
Run this 5-step check before launching any new cold email campaign from a Google Workspace inbox. It takes under 10 minutes and eliminates the most common infrastructure failure mode.
1️⃣Run MX Lookup on mxtoolbox.com
Enter your sending domain. Confirm all five Google MX servers appear with correct priority values. Any non-Google entry is a red flag — remove it.
2️⃣Verify SPF Includes Google's Servers
Your SPF record must include include:_spf.google.com. Run an SPF lookup on the same domain. If your SPF references a different provider's include, add Google's alongside it — or fix the mismatch entirely.
3️⃣Check DKIM Selector in Google Admin
In Google Admin console, go to Apps → Google Workspace → Gmail → Authenticate Email. Confirm DKIM is active and the selector (usually "google") is publishing correctly. A DKIM record that exists but isn't activated in Admin is a common setup error.
4️⃣Send a Test to mail-tester.com
Send a plain-text test email to the address mail-tester.com provides. A score of 9/10 or 10/10 confirms full authentication and MX consistency. Anything lower — look at which check failed first.
5️⃣Check Google Postmaster Tools After 48 Hours
Add your sending domain to postmaster.google.com and wait 48 hours after your first sends. A Good or High domain reputation confirms your infrastructure is being read correctly. Unknown or Low — something in the setup chain is still broken.
3 MX Mistakes That Kill Cold Email Domains
These aren't edge cases. We see all three regularly when teams bring broken domains to us at Litemail.
Mistake 1: Cloudflare Mail Routing Left Active
Cloudflare's mail routing feature is useful for personal domains. It is destructive for cold email sending domains. If Cloudflare mail routing is active, your MX records point to Cloudflare's servers — not Google's. Even if you're sending from Google Workspace via SMTP, the mismatch is visible to recipients. Disable Cloudflare mail routing entirely and set Google MX records manually in Cloudflare's DNS panel.
Mistake 2: Registrar Default MX Records Not Removed
Most domain registrars add default MX records when you register a domain — pointing to their own mail hosting. When you add Google Workspace MX records later, teams often add them without deleting the registrar defaults. Result: duplicate MX records pointing to two different mail systems. Always delete registrar default MX records before adding Google's.
Mistake 3: Only Adding the Primary MX Record
ASPMX.L.GOOGLE.COM at priority 1 is not enough on its own. Some DNS guides show only the primary record. You need all five. Receiving servers that run full MX checks will see an incomplete record set — another trust signal failure. Add all five. Every time.
💡 One More Thing People Miss
If you're using a domain registrar's parking page or DNS redirect on a cold email domain, that can also interfere with MX resolution. Cold email domains should have DNS managed in one place — ideally Cloudflare (with mail routing off) or directly at the registrar — with no redirects active.
How Litemail Handles MX Setup So You Don't Have To
Every Litemail pre-warmed Google Workspace inbox ships with MX records already configured and verified. The five Google mail servers are set at correct priorities before delivery. SPF, DKIM, and DMARC are pre-configured. You receive the inbox ready to send — not ready to troubleshoot.
At $4.99/inbox, that includes the full DNS stack. In our testing across 400+ inboxes delivered in Q1 2026, we haven't had a single MX mismatch failure on a Litemail-provisioned domain. The pre-configuration step is part of the delivery process — not an optional add-on.
Compare that to buying a fresh domain, adding it to Google Workspace yourself, and walking through MX setup manually. One wrong priority value. One forgotten alternate record. One Cloudflare setting left on. Any of those puts you back at the start — and you won't know it until you're 1,000 emails deep into a broken campaign.
Set Up Smarter — Skip the DNS Troubleshooting
Litemail pre-warmed Google Workspace inboxes ship with MX, SPF, DKIM, and DMARC pre-configured. $4.99/inbox. No manual DNS setup. No mismatch risk. Full admin access from day one.
Get Pre-Warmed Inboxes from $4.99 →
Automated DNS setup · Dedicated US and EU IPs · No minimum order · Works with all major platforms via OAuth
About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach. From $4.99/inbox with automated DNS, dedicated US and EU IPs, and full admin access. View pre-warmed inbox plans →
Related reading:
SPF, DKIM, DMARC Auto-Setup for Pre-Warmed Inboxes 2026 · Google Workspace Cold Email Domain Setup · Cold Email Deliverability Guide 2026 · Best Pre-Warmed Inbox Providers 2026 (Ranked) · How Pre-Warmed Inboxes Improve Cold Email Deliverability 2026
Key Takeaways
MX record mismatch is one of the most common and least-checked cold email deliverability failures — it doesn't bounce, it just routes to spam silently.
Google Workspace cold email domains need all five MX records set correctly: ASPMX.L.GOOGLE.COM at priority 1, ALT1 and ALT2 at priority 5, ALT3 and ALT4 at priority 10.
Always delete registrar default MX records before adding Google's — duplicate MX configurations are a trust signal failure for receiving servers.
Cloudflare mail routing must be disabled on cold email domains. It overwrites your MX records with Cloudflare's servers, creating a mismatch that hurts inbox placement.
Run mxtoolbox.com, mail-tester.com, and Google Postmaster Tools before every new campaign. These three checks take under 15 minutes and catch 90% of infrastructure failures.
Litemail pre-warmed GWS inboxes ship with all five MX records pre-configured — no manual setup, no mismatch risk, $4.99/inbox.
Frequently Asked Questions
What is MX matching for Google Workspace cold email?
MX matching means your sending domain's MX records correctly point to Google's mail servers — all five of them, at the right priorities. When MX records match your sending infrastructure, receiving mail servers see a consistent, legitimate domain setup. Mismatches — where MX records point to a different provider than the one you're sending from — trigger spam folder placement even on fully warmed inboxes.
How do I check if my Google Workspace MX records are correct?
Go to mxtoolbox.com and run an MX lookup on your sending domain. You should see five Google mail servers: ASPMX.L.GOOGLE.COM (priority 1), ALT1 and ALT2 at ASPMX.L.GOOGLE.COM (priority 5), and ALT3 and ALT4 (priority 10). If you see any non-Google entries, or if any of the five are missing, fix those first before sending campaigns.
Why is only having the primary MX record a problem?
Some DNS setup guides only show the primary MX record (ASPMX.L.GOOGLE.COM at priority 1). That's enough for basic mail delivery but receiving servers that run thorough infrastructure checks will flag an incomplete MX record set as a trust signal issue. All five Google MX records should be present and set to correct priorities.
Does Cloudflare interfere with Google Workspace MX records?
Yes — if Cloudflare's mail routing feature is enabled on your domain, it overwrites your MX records with Cloudflare's mail servers. You need to disable Cloudflare mail routing entirely and manually set Google's five MX records in Cloudflare's DNS settings. This is one of the most common MX mismatch causes for cold email senders using Cloudflare for DNS management.
Will fixing MX records improve my inbox placement immediately?
Yes, usually within 24 to 48 hours of the DNS change propagating. MX records have relatively low TTL values (typically 3,600 seconds / 1 hour), so propagation is fast. After fixing MX records, check Google Postmaster Tools after 48 hours to confirm domain reputation is reading correctly.
Do Litemail pre-warmed inboxes have correct MX records already?
Yes. Every Litemail Google Workspace inbox ships with all five MX records pre-configured at correct priorities. SPF, DKIM, and DMARC are also pre-configured automatically. You receive a fully verified, campaign-ready inbox — not a setup project. This is included in the $4.99/inbox price with no additional DNS configuration required from your side.
Buy Pre-Warmed Email Inboxes & Domains | Litemail
Pre-warmed Google Workspace inboxes with automated MX, SPF, DKIM, and DMARC setup. From $4.99/inbox. Delivered in 24 hours. No DNS headaches.
View Plans & Pricing →
Related reading:
SPF, DKIM, DMARC Auto-Setup 2026 · Google Workspace Domain Setup · Cold Email Deliverability Guide 2026 · Best Pre-Warmed Inbox Providers 2026 · SPF Record Errors Troubleshooting
