What are the MX records for Google Workspace?

MX (Mail eXchange) records tell the internet where to deliver email for your domain. When you move email to Google Workspace, you replace your domain's existing MX records with Google's so that all incoming mail routes to Gmail. Google changed its recommended setup in 2023, so there are now two valid configurations — the modern single record and the legacy five-record set. Both are documented in Google's Set up MX records help page.

The modern Google Workspace MX record (recommended)

As of 2023, Google recommends a single MX record. This is what new domains should use:

Type      MX
Host      @  (or blank — the root of your domain)
Priority  1
Value     smtp.google.com

That is the entire configuration. One record, priority 1, pointing at smtp.google.com. Google states directly that "The Google Workspace MX record value is smtp.google.com." Some registrars want a trailing dot (smtp.google.com.) and some combine priority and host on one line (1 smtp.google.com) — follow your registrar's format, but the value and priority never change.

The legacy 5 ASPMX records (still supported)

Domains that started on Google Workspace before 2023 often still run the older five-record set, which starts with aspmx. Google confirms these "are still supported," so if your email works, you do not need to change anything. The legacy set is:

Priority  Value
1         ASPMX.L.GOOGLE.COM
5         ALT1.ASPMX.L.GOOGLE.COM
5         ALT2.ASPMX.L.GOOGLE.COM
10        ALT3.ASPMX.L.GOOGLE.COM
10        ALT4.ASPMX.L.GOOGLE.COM

Here ASPMX.L.GOOGLE.COM at priority 1 is the primary server, and the four ALT servers are progressively lower-priority backups. Any account can switch from this legacy set to the single smtp.google.com record, but there is no requirement to do so while mail is flowing.

How MX priority works

Lower numbers mean higher priority. A sending server tries the MX record with the lowest preference number first, and only falls back to higher numbers if the primary is unreachable. That is why the primary server is priority 1 in both setups. If you mix the two configurations or leave an old provider's MX record behind at a lower number, mail can route to the wrong place — which is the single most common cause of "we moved to Google but email still goes to the old host."

Do not mix configurations

Use either the single smtp.google.com record or the legacy five-record set — never both, and never alongside your previous provider's MX records. Before you add Google's MX records, delete every existing MX record on the domain. Leftover records are the top setup mistake and routinely break inbound delivery.

Common Google Workspace MX mistakes

A handful of errors account for most "Gmail not receiving mail" tickets after a migration:

• Leaving the old provider's MX records in place. If your previous host's MX record sits at a lower priority number than Google's, mail keeps flowing to the old mailbox. Always remove old MX records.
• Adding both the modern and legacy sets. Running smtp.google.com and the five ASPMX records at once creates ambiguous routing. Pick one configuration.
• Pointing MX at a hostname that does not resolve. A typo like smtp.googl.com produces silent delivery failures. The DNS lookup tool catches this immediately.
• Wrong host/name field. MX records belong at the root of the domain (@ or blank), not at www or mail. For a subdomain like support.example.com, enter the subdomain label in the host field.
• Skipping Gmail activation. Publishing MX records is only half the job — you still click "Activate Gmail" in the Admin console for the domain.

MX records for a subdomain

If you run Google Workspace on a subdomain (for example mail.example.com), add the same smtp.google.com MX record but set the host field to the subdomain label rather than @. The priority and value stay identical; only the host changes. This is common when a root domain keeps a different mail provider and a subdomain is delegated to Google Workspace.

Propagation and verification

After you change MX records, Google says it can take up to 72 hours for the change to be recognized across the internet, though it is often much faster. To confirm the change is live:

1. Use the DNS lookup tool to query your domain's published MX records and confirm they match smtp.google.com (or the legacy ASPMX set) with the right priorities.
2. Run the free email security test to verify mail routing alongside SPF, DKIM, and DMARC in one pass.
3. In the Google Admin console, complete the "Activate Gmail" step — MX records published correctly still need Gmail activated for the domain.

MX records are only half of email setup

Correct MX records get mail into Gmail, but to send out reliably you also need authentication. Pair this with the Google Workspace SPF record (v=spf1 include:_spf.google.com ~all), DKIM signing, and a DMARC policy. Google's sender requirements explain why all three are now mandatory for reliable delivery, and the SPF fundamentals guide walks through the authentication side step by step.