Google Workspace MX Records: The Correct Values and How to Add Them at Any Registrar
Your domain is verified, your users exist, and Gmail is still empty. That is almost always an MX record problem. Below are the exact Google Workspace MX records (both valid sets), where to paste them at GoDaddy, Namecheap, Cloudflare, Squarespace, Porkbun, Hostinger, Bluehost and Wix, and how to prove they are live.
The correct Google Workspace MX records (and what they do)
An MX (Mail Exchange) record is the line in your domain’s DNS that tells every other mail server where to deliver messages for anything@yourdomain.com. Senders look up your MX records, try the lowest priority number first, and hand over the message. Google does not control your DNS; your registrar does, or whichever service your nameservers point to. Until your MX settings point at Google, incoming mail keeps going to your old host, or nowhere. MX records only affect incoming mail: your users can send from Gmail immediately, but replies will not come back until this is right.
Google simplified the setup in 2023. Domains configured before then were given five records, the “ASPMX” set still shown in older G Suite MX records tutorials; new setups get a single record, smtp.google.com. Google’s Set up MX records for Google Workspace page says any account can use the single record, the legacy values are still supported, and if your mail already works, no change is required.
| Record set | Name / Host | Type | Priority | Value / Points to | TTL |
|---|---|---|---|---|---|
| New single record (Google’s recommendation for new setups) | @ or blank | MX | 1 | smtp.google.com | Registrar default (often 3600) |
| Legacy five-record set (still valid for existing domains) | @ or blank | MX | 1 | ASPMX.L.GOOGLE.COM | 3600 |
@ or blank | MX | 5 | ALT1.ASPMX.L.GOOGLE.COM | 3600 | |
@ or blank | MX | 5 | ALT2.ASPMX.L.GOOGLE.COM | 3600 | |
@ or blank | MX | 10 | ALT3.ASPMX.L.GOOGLE.COM | 3600 | |
@ or blank | MX | 10 | ALT4.ASPMX.L.GOOGLE.COM | 3600 |
Heads-up: use one set, never both, and never leave another provider’s MX record next to either. If you move from the five legacy records to the single one, delete all five and add
smtp.google.comin the same editing session.
Formatting quirks: some registrars need a trailing period (smtp.google.com.), some combine priority and value in one field (1 smtp.google.com), and for a subdomain such as support.yourdomain.com the host is support, not @. Case does not matter. And despite its name, smtp.google.com is an inbound MX target, not an outgoing server for Outlook or a printer; those use smtp.gmail.com.
Before you start
- Verify your domain first. Google will not activate Gmail on an unverified domain. See How to Verify Your Domain for Google Workspace.
- Create your users before you switch. Once MX records point at Google, mail to any address that does not exist in Workspace bounces. See How to Add Users to Google Workspace.
- Know where your DNS lives. If your nameservers point to Cloudflare or your web host, edit MX records there, not at the registrar. Google’s Admin Toolbox Dig tool with the NS option tells you.
- Have the right access. A super admin (or an admin with the Domain settings privilege) at
admin.google.com, plus your registrar login and its two-factor device. - Moving from another provider? Mail keeps arriving at the old host until the change propagates, so keep those mailboxes reachable for a few days. Our Gmail migration guide covers moving existing mail.
14-day free trial · 10% off your first year with our referral link
Step 1: Open the Gmail setup in the Admin console
Option A: the setup wizard (recent sign-ups)
If you signed up recently, the Admin console home page shows a Setup tool covering domain verification, users and Gmail activation. Its Gmail step shows the MX value to add and links to registrar instructions; for some registrars it can sign in to your domain host and add the record for you, in which case skip Steps 2 and 3. Otherwise keep the wizard open in one tab and do the registrar work in another.
Option B: the manual path (existing accounts, extra domains)
Go to Admin console → Menu → Account → Domains → Manage domains, click Activate Gmail next to the domain and follow the steps on screen. This is also the path for a secondary domain (see Add Multiple Domains to Google Workspace); every domain needs its own MX record.
How to check it worked: you can see the MX value Google wants and an Activate Gmail button. Do not click it yet.
Step 2: Delete the old MX records at your registrar
Sign in to your registrar or DNS host, open the domain’s DNS records, screenshot the current list, and delete every record of type MX that is not Google’s.
This is the step people skip, and it is the classic cause of “email works for some users but not others”. Sending servers choose between all the MX records they find, so if your old host’s record is still there, a share of your mail keeps landing on the old server. Users who still have a mailbox there see it arrive in the wrong inbox, new users get bounces, and the pattern looks random. Google’s help page is blunt: email might not work correctly if you keep old or incorrect MX records.
While you are in the DNS editor, also remove:
- A CNAME on the bare domain (
@). Namecheap warns that a CNAME there overrides every other record, including MX. - Email forwarding or routing presets (Cloudflare Email Routing, website-builder forwarding). They install their own MX records.
- The previous provider’s records. For Microsoft 365 the target ends in
mail.protection.outlook.com; for cPanel hosts it is usuallymail.yourdomain.com.
How to check it worked: the only MX records left are Google’s, or the list is empty and ready for Step 3.
Step 3: Add the Google MX record at your registrar
The record is the same everywhere: type MX, host @ (or blank), priority 1, value smtp.google.com, TTL at the registrar’s default. Only the menu labels change.
GoDaddy
Open the domain’s DNS management page, delete the existing MX records, then add a record with Type MX, Name @, Priority 1, Value smtp.google.com and TTL left at Default. If the Admin console cannot find it straight away, give GoDaddy about an hour and retry.
Namecheap
Go to Domain List → Manage → Advanced DNS, scroll to Mail Settings and choose Custom MX (Namecheap’s MX guide flags its Gmail preset as not working). Enter host @, value smtp.google.com, priority 1, TTL Automatic, and save. Namecheap says changes normally take about 30 minutes.
Cloudflare
Go to DNS → Records → Add record: Type MX, Name @, Mail server smtp.google.com, Priority 1, TTL Auto. MX records have no proxy toggle; they are always DNS-only. The orange cloud matters for any A or CNAME record that mail depends on, such as a mail CNAME for a custom URL: set those to DNS only. Also, if Email Routing is on, it owns your MX records (route1.mx.cloudflare.net and friends) and Cloudflare’s documentation says it cannot be used with external mail servers. Disable it from its Settings page.
Squarespace (including former Google Domains)
At account.squarespace.com/domains open the domain, click DNS, open Add preset and choose Google Workspace MX. Squarespace’s help page allows up to 48 hours, and says that if the Admin console reports a “Conflicting DNS record”, delete any existing MX, DKIM, SPF and email-forwarding records and retry. If you sign in to Squarespace with an address on this domain, change your account email first.
Porkbun
In Domain Management, click Details next to the domain, open the DNS Records editor, click Add record, switch to the Quick Setup tab and choose Google Workspace. Porkbun’s guide notes this adds both the MX record and an SPF TXT record, and that the newer record also works for pre-2023 accounts.
Hostinger
In hPanel go to Domains → Manage → DNS / Nameservers, and under Manage DNS records add type MX, name @, mail server smtp.google.com, priority 1, TTL 3600. Hostinger’s Workspace guide says to remove existing MX, SPF, DKIM and DMARC records for other email services first and to allow a few hours for propagation.
Bluehost
Bluehost’s DNS records for email services page lists both Google sets and says not to mix them. Edit via Bluehost Portal → Hosting → cPanel Email → MX Entry, add Google’s record, delete the others, then set Email Routing to Remote Mail Exchanger. Bluehost warns that editing MX records can reset this; if it stays on local delivery, cPanel quietly keeps your mail on the server.
Wix
Go to Domains, click the Domain Actions icon, select Edit MX Records, pick Google Workspace from the dropdown and save. If your domain is connected to Wix “by pointing”, the MX records live at your domain host instead, as Wix’s help article explains.
Any other registrar or DNS host
Look for DNS, DNS Zone, Advanced DNS or Records. Google’s help page links to instructions for IONOS, Amazon Route 53, cPanel, Shopify and Crazy Domains. If your host auto-appends your domain to the value, add the trailing period.
How to check it worked: the record list shows exactly one MX record for @ pointing to smtp.google.com with priority 1 (or the five ASPMX records), and nothing else of type MX.
14-day free trial · 10% off your first year with our referral link
Step 4: Activate Gmail, wait for propagation, and verify
Click Activate Gmail (and understand TTL)
Back in the Admin console, click Activate Gmail (or the equivalent button in the wizard). Google looks up your MX records and confirms they point to its servers. If it cannot find them, it is almost always timing: Google’s official figure is up to 72 hours, although most registrars publish within an hour. Wait and retry; do not add the records again.
TTL (time to live) causes the delay: it is how many seconds other servers may cache your DNS answer. An old MX record with a TTL of 86400 can keep being used for a full day. If you can, lower the old record’s TTL to 300 the day before you switch, and leave Google’s record at the default.
Run an MX record lookup
Do not trust the registrar’s screen; check what the internet sees. Google Admin Toolbox Check MX tests your MX and SPF records (and DKIM if you enter a selector) and flags leftover non-Google records. Admin Toolbox Dig with the MX option shows the raw records and priorities. On a computer, nslookup -type=mx yourdomain.com (Windows) or dig yourdomain.com MX (Mac, Linux) gives the same answer. A correct result lists exactly 1 smtp.google.com or the five ASPMX entries; anything extra is a leftover from Step 2.
Then email one of your users from an outside account and reply. If a message goes missing, Google’s troubleshooting page points you to Email Log Search in the Admin console, which traces messages from the past 30 days.
How to check it worked: Check MX reports no MX problems, Dig shows only Google’s records, and your test email lands in the Workspace inbox.
The other Google Workspace DNS records you will be asked for
MX is one of several Google Workspace DNS records. Here is the full set.
| Record | Host | Value | Purpose |
|---|---|---|---|
| TXT (verification) | @ | google-site-verification=… | Proves you own the domain |
| MX | @ | smtp.google.com, priority 1 | Routes incoming mail to Gmail |
| TXT (SPF) | @ | v=spf1 include:_spf.google.com ~all | Authorises Google to send for your domain |
| TXT (DKIM) | google._domainkey | 2048-bit key generated in the Admin console | Signs outgoing mail so it cannot be forged |
| TXT (DMARC) | _dmarc | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com | Policy for failures, plus reports |
| CNAME (optional) | mail, calendar, drive | ghs.googlehosted.com | Custom URLs such as mail.yourdomain.com |
SPF, DKIM and DMARC decide whether the mail you send is trusted; since February 2024 Gmail and Yahoo require all three from senders of 5,000 or more messages a day. Google’s pages are Set up SPF, Set up DKIM and Set up DMARC. Two timing rules from them: generate the DKIM key at Admin console → Apps → Google Workspace → Gmail → Authenticate email only after Gmail has been active for 24–72 hours, and allow 48 hours after SPF and DKIM before adding DMARC. Our walkthrough is SPF, DKIM & DMARC for Google Workspace.
The CNAME records are optional vanity addresses. Under Admin console → Menu → Account → Account settings → Custom URLs you choose a prefix such as mail, then add a CNAME at your registrar pointing it to ghs.googlehosted.com (see Customize a Google Workspace service URL). They are optional, and Google notes they are unavailable on domains that enforce HTTPS via HSTS.
Common mistakes and troubleshooting
- Mail arrives for some users only. An old MX record is still published. Run Check MX, delete every non-Google MX record and wait for the old TTL to expire.
- Typos in the host name. The legacy host is spelled with the letter L,
ASPMX.L.GOOGLE.COM, and the new value issmtp.google.com, notsmtp.gmail.com. - The registrar appended your domain. Dig shows
smtp.google.com.yourdomain.com. Re-enter the value with a trailing period. - You edited DNS in the wrong place. If nameservers point to Cloudflare or your web host, records at the registrar are ignored. Check with a Dig NS lookup.
- Something else is intercepting mail: a CNAME on the bare domain, Cloudflare Email Routing, or cPanel local mail routing (switch it to Remote Mail Exchanger).
- Mail arrives but your replies land in spam. Not an MX problem. Set up SPF, DKIM and DMARC.
Once mail is flowing, most small teams next set up catch-all email for misspelled addresses and forwarding and routing rules for info@ and support@. Still choosing a plan? Our pricing page compares Business Starter ($8.28), Standard ($16.56) and Plus ($25.83) per user per month.
14-day free trial · 10% off your first year with our referral link
Related setup guides
- All Google Workspace setup guides
- How to Set Up Google Workspace: Complete Guide
- How to Verify Your Domain for Google Workspace
- SPF, DKIM & DMARC for Google Workspace
- How to Add Users to Google Workspace
- Migrate Outlook or Microsoft 365 to Google Workspace
- Custom domain email with Google Workspace
- Setting up Google Workspace for a small business
Frequently asked questions
What are the Google Workspace MX records?
For new setups Google recommends one MX record: host @, priority 1, value smtp.google.com. Domains configured before 2023 may still use the legacy set of five: ASPMX.L.GOOGLE.COM at priority 1, ALT1.ASPMX.L.GOOGLE.COM and ALT2.ASPMX.L.GOOGLE.COM at priority 5, and ALT3.ASPMX.L.GOOGLE.COM and ALT4.ASPMX.L.GOOGLE.COM at priority 10. Both sets are valid; use one or the other, never both.
Should I use smtp.google.com or the ASPMX records?
Use smtp.google.com for any new domain or new Google Workspace account; it is what the Admin console shows you. If your domain already has the five ASPMX records and mail works, Google says no change is required. Switching is optional, and if you do it, replace all five records in one editing session.
Can I mix the new and old Google MX records?
Do not. Both sets route mail to Google, but a hybrid is not what Google’s setup checker or registrar presets expect, and it makes problems harder to diagnose. Pick one complete set, delete everything else of type MX, and confirm the result with the Google Admin Toolbox Check MX tool.
How long do MX records take to propagate?
Google’s official guidance is up to 72 hours, but most registrars publish changes within an hour and often within minutes. The delay comes from the TTL on your old record, which lets other mail servers cache the previous answer. If the Admin console cannot find your records, wait and retry rather than adding them again.
Why do only some of my users receive email after switching to Google Workspace?
Almost always because an old MX record from your previous email host is still published alongside Google’s. Sending servers pick between the records they find, so part of your mail keeps going to the old server. Delete every non-Google MX record, check with an MX lookup, and keep the old mailboxes reachable until the old TTL expires.
Do old G Suite MX records still work?
Yes. Google states that the legacy ASPMX values, which many domains added as G Suite MX records before 2023, are still supported, and that any account can also move to the single smtp.google.com record. If your email is arriving correctly, there is nothing to change.
Does Google Workspace need other DNS records besides MX?
Yes. You need a TXT record to verify domain ownership, and you should add SPF (v=spf1 include:_spf.google.com ~all), a DKIM key generated in the Admin console, and a DMARC policy so your outgoing mail is trusted. Optional CNAME records pointing to ghs.googlehosted.com give you custom URLs such as mail.yourdomain.com.
MyOwnGoogle is reader-supported. If you start a Google Workspace trial through our links we may earn a commission, at no extra cost to you. This never affects what we recommend.