DNS
Google Workspace DNS record generator
Get the one MX record and SPF include Google Workspace documents, and a plain answer about the old "aspmx" records.
Free, no accountIn your browser
The records below do not change with this, but the page will name your own domain rather than a generic one.
Result
MX and SPF ready for your domain
Add these as MX and TXT records at the root of your domain, then add DKIM and verification from the Admin Console.
- Info
The MX and SPF records below do not need your domain
Google publishes the same MX target and SPF include for every Workspace account, so there is nothing to fill in to get them right. Typing your domain only makes this page name it instead of speaking generically.
- Info
An older domain may already have different, still-supported MX records
Google's own current help page says a domain set up before the single record existed "might have different MX record values that start with 'aspmx'" and that Google still supports them - it does not list what they are, and this generator will not print values Google itself no longer documents.
If this domain already has MX records starting with "aspmx", leave them as they are rather than replacing them with the single record above - both are supported, and switching is not required.
- Info
DKIM is generated per account, not published here
Google generates a distinct DKIM key for every Workspace account, so there is no fixed TXT value this generator could print - a realistic-looking placeholder here would be wrong for every domain that pasted it.
Open the Google Admin Console, go to Apps > Google Workspace > Gmail > Authenticate email, and copy the DKIM TXT record it generates there for this domain.
- Info
The domain-verification token is also account-specific
Google issues a one-time verification TXT or HTML-file token when a domain is added to Workspace, unique to that signup - there is no fixed value a generator could emit for it.
Open the Google Admin Console setup wizard for this domain and copy the verification value it shows there.
- Passed
One MX record is what Google now documents
Google Workspace issues this single record to every domain signing up today, and its own setup help page no longer lists a multi-record alternative to choose instead.
- Passed
One SPF record, with Google Workspace as the only sender
This assumes Google Workspace is the only thing sending mail as this domain. Add another provider through the SPF generator next door rather than editing this line by hand.
MX record to publish
At @ (MX)
Priority then host, at the root of the domain, not a subdomain. Leave an existing "aspmx" MX setup alone rather than replacing it with this.
SPF record to publish
At @ (TXT)
Publish this at the domain itself. A domain may only have one SPF record - add senders to this one rather than publishing a second.
DNS records for your domain
| Host | Type | Value | Priority |
|---|---|---|---|
| @ | MX | smtp.google.com | 1 |
| @ | TXT | v=spf1 include:_spf.google.com ~all | - |
DKIM and the domain-verification token are missing on purpose - both are generated per Workspace account and only ever shown inside the Admin Console.
Still to do in the Admin Console
Copy the DKIM TXT record from Apps > Google Workspace > Gmail > Authenticate email, and publish it alongside the records above.
Copy the domain-verification value from the setup wizard for this domain, and publish or upload it as Google asks.
- The DKIM TXT value and the domain-verification token are unique per Workspace account and only ever appear in the Admin Console - this tool cannot generate either and does not guess at a value.
- An older domain may already carry different MX records starting with "aspmx" from before the single record above existed; Google still supports them but no longer publishes what they are, so none is printed here.
What this is
This Google Workspace DNS records generator writes the single MX record and SPF include Google documents for Workspace today, and says plainly where the account-specific values - DKIM and domain verification - actually live, rather than guessing at any of the four.
Google Workspace issues one MX record, `smtp.google.com` at priority 1, to every domain signing up today. Google's own current setup help page no longer documents a multi-record alternative - it only says an older domain might already have different MX values starting with "aspmx", which it still supports without listing what they are.
SPF is one include naming Google Workspace as an authorised sender, the same line for every account. DKIM and the domain-verification token are the opposite: both are minted per Workspace account inside the Admin Console, and neither has a fixed value this or any generator could print.
For how MX and SPF fit alongside the other records a domain needs, and why TXT is the type that carries SPF at all, see our blog guide "The DNS records a domain needs, and what each one actually does."
How to read the result
The MX and SPF records below are correct for any domain the moment they are published, current or brand new - neither one depends on what this domain had before.
The finding about "aspmx" records is not an error: it exists so a domain that already has an older MX setup is not pushed to replace something that still works with a record this page cannot even confirm matches what it had.
Common mistakes
What goes wrong most often, and how to tell.
- Replacing a working "aspmx" MX setup with the single current recordGoogle still supports an older MX setup that already answers for this domain. Switching to the single record is not required, and doing so before confirming mail still routes correctly risks a gap this generator has no way to detect.
- Pasting a placeholder DKIM value instead of the Admin Console copyNo DKIM value prints on this page because there is no single correct one - it is generated per account inside the Admin Console, and a value copied from anywhere else will not match the key Google actually signs with.
- Publishing a second SPF record for Google Workspace alongside an existing oneA domain is only allowed one SPF TXT record. The Google Workspace include needs to be added as one more term inside the existing record, not published as a second one that breaks SPF checking for every sender.
Questions
What people ask about this tool.
- Google's current setup documentation says an older domain "might have different MX record values that start with 'aspmx'" and that Google still supports them, but it no longer lists what those values are - so this generator will not print them. Leave an existing "aspmx" setup as it is rather than replacing it.
- Google generates a different DKIM key for every account, so there is no fixed value a generator can print. Open the Admin Console, go to Apps > Google Workspace > Gmail > Authenticate email, and copy the DKIM TXT record shown there for this domain.
- Google issues a one-time verification value tied to the specific signup that added this domain to Workspace, so it is never the same for two domains and never reusable - it only ever appears in the Admin Console's own setup wizard for that domain.
- Yes - MX, SPF and DKIM only get mail delivered and authenticated; none of them says what a receiver should do with a message that fails. The DMARC generator next door builds that policy once this record and the Admin Console's DKIM key are both live.
Sources
Every fixed value here comes from the provider’s own documentation. These pages change, so each says the day it was last read.
- Google, “Set up MX records for Google Workspace” read 12 October 2026
- Google, “Set up SPF” read 12 October 2026
Use it from the API
The same check, as one request.