Google Workspace records at Namecheap
Google gives you each value in the Google Admin console. Add them in this order: verification first, the mail record once the new mailboxes are ready, then the three records that keep your mail out of spam.
| Record | Host | Value |
| Verify the domainTXT | @ | google-site-verification= followed by your code from the Admin console |
| Receive mailMX, priority 1, under Custom MX | @ | smtp.google.com |
| SPFTXT | @ | v=spf1 include:_spf.google.com ~all |
| DKIMTXT | google._domainkey | The key starting v=DKIM1; that the Admin console generates for you |
| DMARCTXT | _dmarc | v=DMARC1; p=none; rua=mailto: followed by an address you read |
Verifying the domain
In the Admin console, go to Account, Domains, Manage domains, and select Verify domain. If Google asks who your domain host is, pick Namecheap, as Namecheap's Google Workspace guide shows. Copy the whole value, including google-site-verification=, and add it under Host Records as a TXT record with @ as the host. Leave it in place until Google confirms, which Google says can take up to 72 hours. This record proves you own the domain and does not change where your email goes, so it is safe to add while your current email keeps working. If Google still refuses, the usual causes are in Google Workspace domain verification failed.
Pointing mail at Google
Under Mail Settings, choose Custom MX and add one record: host @, value smtp.google.com, priority 1 (Namecheap's Google Workspace guide). Google says to remove any other MX records, because leftovers can stop mail working. If Mail Settings was on Email Forwarding or Private Email, choosing Custom MX moves your mail away from that service, and Namecheap says its free forwarding cannot run beside another email service. So make this change only when the new mailboxes exist. If your Workspace account dates from before April 2023 and uses Google's older values that start with aspmx, and your mail works, Namecheap's guide agrees nothing needs to change.
SPF, DKIM and DMARC
For SPF, Google's value when Workspace is your only sender is v=spf1 include:_spf.google.com ~all. If an SPF record already exists, edit it rather than adding a second, and put any other service that sends as you in the same record (Google's SPF guide). One Namecheap catch: with Private Email chosen in Mail Settings, Namecheap adds that service's SPF record itself and does not list it on the Advanced DNS page. After the switch, run our free SPF checker to see that exactly one SPF record answers, and that it names Google.
For DKIM, wait 24 to 72 hours after Gmail is turned on. Then, in the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email, and generate a new record. Add it under Host Records as a TXT record with google._domainkey as the host, and only then select Start authentication (Google's DKIM guide). Namecheap supports both 1024 and 2048 bit keys.
Add DMARC last. Google suggests waiting 48 hours after SPF and DKIM, then starting at p=none, which only reports and blocks nothing, and tightening it once the reports show your real mail passing (Google's DMARC guide). Namecheap's general TXT guide shows a DMARC example set to reject; it shows the format, not a safe place to start.