# Set up SPF, DKIM and DMARC for Google Workspace

If your mail runs on Google Workspace, three DNS records let receivers trust it: SPF names Google's servers, DKIM signs each message with your own key, and DMARC tells receivers what to do with mail that has no SPF or DKIM pass for the domain in its From address. You change DNS at your DNS provider, or in MailGlo if it hosts your records; only DKIM needs the Google Admin console. The Google steps come from Google's admin help, which we read on 14 November 2026.

## Before you start

1. You need a super administrator account in Google Workspace for the DKIM steps.
2. You need access to your domain's DNS, usually where you bought the domain.
3. List every service that sends mail as your domain besides Gmail: a newsletter tool, invoicing, a support desk, website forms. Each needs its own SPF entry or DKIM key. [Check a domain](/check/) shows your current SPF and DMARC records.
4. If your mail leaves Google through a relay or gateway that changes messages, for example by adding a footer, ask whoever runs it to leave messages unchanged. Google warns that a changed message can fail DKIM.
5. The steps in MailGlo need your domain added there ([Add and verify your domain](/docs/add-a-domain/)). The domain's tabs, Senders among them, appear once its setup is complete, and setup asks for your DMARC record. Since Google suggests DMARC last, do sections 1 and 2 first, then finish setup in section 3. If MailGlo hosts your SPF record, finish setup before section 1, which uses the Senders tab.

## 1. SPF: allow Google's servers

Google's value for a domain that sends only through Google Workspace ([Set up SPF](https://knowledge.workspace.google.com/admin/security/set-up-spf), updated 10 November 2026):

```
v=spf1 include:_spf.google.com ~all
```

If MailGlo hosts your SPF record, don't edit it at your DNS provider: your record holds only MailGlo's name, and MailGlo serves the services you allow behind it. Add Google in MailGlo instead. The Senders tab appears once the domain's setup is complete; if it's still in setup, finish setup first, as [section 3](/docs/google-workspace/#3-dmarc-start-with-monitoring-and-reports) step 1 explains, then come back here.

1. Open the domain's Senders tab. Allow every other service under New that sends for you. If your record still serves a service you answered Not mine for, MailGlo can't change it in one step and answers with **Details →**. Leave that form: a change made there keeps only the services you tick.
2. Choose Add a service, pick Google Workspace, then Allow it. If Google Workspace is already under New, choose Decide, then Yes, allow it.

MailGlo adds `include:_spf.google.com` and keeps the other services. The free plan hosts up to 3 services ([Hosted SPF](/docs/spf/#hosted-spf)): if your record already has 3, MailGlo says so and changes nothing. To add Google as a fourth, choose a paid plan, which hosts any number.

If you can't change DNS records in MailGlo, the change waits for someone in your workspace who can. Two cases need us. One is that **Details →** answer, for a service you answered Not mine for. The other is Google Workspace already under Allowed while To do still has an item for it. In either case, email support@mailglo.com with your domain and `include:_spf.google.com` ([Get help](/docs/report-a-problem/)). We check your record and your plan, and reply with what we can change.

Until Google is in your record, mail from Google fails SPF; under `p=quarantine` or `p=reject`, mail without your own DKIM key from section 2 may go to spam or be refused.

If you don't use hosted SPF:

1. At your DNS provider, open the TXT records for your domain. Most providers call the domain itself `@`.
2. If a record starting `v=spf1` is already there and doesn't list `include:_spf.google.com`, add it, before the ending (`~all` or `-all`). Don't add a second SPF record: with two, every SPF check of your domain gives an error instead of a pass, and each receiver decides what to do with the mail.
3. If none is there, add a TXT record with the value above.
4. If other services send for you, add their entries to the same record, for example `v=spf1 include:_spf.google.com include:servers.mcsv.net ~all` for Google and Mailchimp. A record may make at most ten lookups ([SPF](/docs/spf/)).

Nothing changes in the Admin console for SPF. A DNS change can take up to 48 hours to reach every receiver.

## 2. DKIM: create the key in the Admin console, then publish it

Until you create your own key, Google Workspace signs your mail with a key for a Google domain ending in `gappssmtp.com`. That signature passes DKIM but can't pass DMARC for your domain, because it isn't your domain.

Your domain may already have its own key: Google says some domains have one by default, such as one bought from a Google partner when you signed up. Check before you create one. Open [Check a domain](/check/), enter your domain and type `google` next to Signing keys. If a key is found and a message you send shows `dkim=pass` for your own domain ([step 4](/docs/google-workspace/#4-check-a-received-message)), DKIM is on: go on to DMARC. If a key is found but mail doesn't pass yet, go to [Turn DKIM on](/docs/google-workspace/#turn-dkim-on) first. Create a new key only if that doesn't help: it replaces the one you have, and mail isn't signed for your domain until the new key is published and authentication is started again.

Google adds one condition: after you turn on Gmail for your Google Workspace account, wait 24 to 72 hours before you create the key, or the Admin console may report that the record was not created ([Set up DKIM](https://knowledge.workspace.google.com/admin/security/set-up-dkim), updated 10 November 2026).

### Create the key

1. Sign in to the Google Admin console as a super administrator and go to Menu, then “Apps”, then “Google Workspace”, then “Gmail”.
2. Click “Authenticate email”.
3. Under “Selected domain”, choose your domain.
4. Click “Generate New Record”.
5. Choose a key length of 2048, and keep the prefix selector `google` unless your domain already has a DKIM key named `google`. Choose 1024 only if your DNS provider can't take a 2048-bit key.
6. Click “Generate”. The page shows “DNS Host name (TXT record name)” and “TXT record value”. Copy both.

Don't click “Start authentication” yet. Google warns that the page may say "You must update the DNS records for this domain" for up to 48 hours; once the record is published, you can ignore it.

### Publish the key

1. At your DNS provider, add a TXT record named `google._domainkey`, or the name the Admin console showed if you changed the prefix. If MailGlo already serves that selector for you, open the domain's DNS records in MailGlo instead, choose Change a record, then the goal "Publish a service's DKIM key".
2. Paste the whole value, starting `v=DKIM1; k=rsa; p=`.
3. If the provider refuses a value longer than 255 characters, split it into several quoted strings, one after another, in the same record. Google's [Troubleshoot DKIM issues](https://knowledge.workspace.google.com/admin/security/troubleshoot-dkim-issues) shows how. MailGlo's own 2048-bit key at `google._domainkey.mailglo.com` is published as two strings.
4. Repeat for each domain you send from. Each domain gets its own key from the Admin console.

To check the key, open [Check a domain](/check/), enter your domain and type your selector, `google` unless you changed it, next to Signing keys.

### Turn DKIM on

1. In the Admin console, go back to Apps, Google Workspace, Gmail, then “Authenticate email”.
2. Choose the domain and click “Start authentication”.
3. The status at the top changes to "Authenticating email with DKIM".

Signing can take up to 48 hours to start after you add the key.

## 3. DMARC: start with monitoring and reports

Google asks you to wait 48 hours after SPF and DKIM work before you publish DMARC ([Set up DMARC](https://knowledge.workspace.google.com/admin/security/set-up-dmarc), updated 10 November 2026). Like SPF, it needs nothing in the Admin console.

A domain has one DMARC record, a TXT record named `_dmarc`. If yours already has one, change its value; don't add a second, and keep the policy (`p=`) it has. Without one, start with `p=none`: receivers take no DMARC action on failing mail, though their own filters still apply, and MailGlo's report address gets the daily reports.

Google warns that reports can reach "hundreds or even thousands" a day for a large company, and recommends a third-party service to read them ([About DMARC reports](https://knowledge.workspace.google.com/admin/security/about-dmarc-reports)). With MailGlo:

1. If the domain's setup isn't complete, open the domain in MailGlo, adding it first if it isn't there yet, and publish the records setup lists, as [Add and verify your domain](/docs/add-a-domain/) explains: the domain access record, and the exact DMARC value, with MailGlo's report addresses added and your current policy and recipients kept, or `p=none` if you have no record yet. At your DNS provider, put that whole DMARC value in the `_dmarc` TXT record, replacing the value there, or add the record if you have none.
2. If the domain's setup is already complete, your DMARC record names MailGlo: leave it as it is. If it has changed since and lost MailGlo's report address, open the domain's DNS records tab, choose Change a record, then the goal "Get daily reports at MailGlo". The change adds MailGlo's report addresses and keeps your policy and recipients. If MailGlo hosts your DMARC record, a CNAME at `_dmarc`, MailGlo publishes the change; otherwise it shows the record to publish at your DNS provider.
3. Receivers send reports about once a day, so the first one usually arrives a day or two after setup is complete. Not every receiver sends reports. Senders lists the services MailGlo found in them and asks you to allow each or mark it as not yours. Compare it with your own list from [Before you start](/docs/google-workspace/#before-you-start): a service that sends rarely may not appear yet.
4. Answer for your own mail first. It can appear under any of three names: Google Workspace, before section 2 or while Google's own `gappssmtp.com` signature still passes; "Unknown service using" your domain, once Google signs with your own key; or the name of an SPF entry in your record that lists Google's servers. A row named "Unknown service using" your domain can also hold mail from others that claims your domain, with a signature that failed. Its page shows how many emails it sent each day and how many passed; if you're unsure the mail is all yours, ask support before you allow it.
5. Allowing your own mail needs no DNS change: Google is already in your SPF record from section 1, and your key from section 2 is published. If MailGlo then offers **Details →**, or To do shows "Finish the DNS change" for that row, leave both: your records already cover this mail, so there's nothing to publish. The To do item then stays, and your mail isn't affected. On a record MailGlo hosts, a change made in that form keeps only the services you tick.
6. Once every service you use passes, strengthen the policy one step at a time: `p=none` to `p=quarantine`, which asks receivers to put failing mail in spam, then `p=reject`, which asks them to refuse it. [DMARC](/docs/dmarc/) explains each policy. To make each step, open the domain's DNS records tab, choose Change a record, then the goal "Turn up protection against spoofing", and pick "Send it to spam (quarantine)" or "Turn it away (reject)". Never lower a policy you already have.
7. While your policy is `p=none`, the health check on the domain's DNS records tab says whether reports show you're ready ([Security score](/docs/security-score/#the-checks)). Before the first reports, its DMARC policy check waits for them and opens Reports. After that, until reports show you're ready, it names the senders still waiting for your answer, or the allowed services that fail DMARC, and opens Senders.
8. At `p=quarantine` that check is green, so before you move to `p=reject`, open Senders and check that every service you use is allowed and its mail passes. If you raise the policy before reports show you're ready, MailGlo asks you to accept the risk before it saves the change.

If people at your domain post to mailing lists, RFC 9989 advises against `p=reject`; [RFC 9989 and mailing lists](/docs/dmarc-rfc-9989/#p-reject-and-mailing-lists) explains why.

Google's rollout page still suggests `pct=10` or `pct=5` for a gradual start. RFC 9989, the current DMARC standard, removed `pct`; [what changed in RFC 9989](/docs/dmarc-rfc-9989/) explains what to use instead.

## 4. Check a received message

Send a message from your domain to a Gmail address at another domain. Google notes that a message to yourself doesn't show whether DKIM works.

1. Open the message in Gmail on a computer.
2. Next to Reply, click More, then “Show original”.
3. Look for `spf=pass`, `dkim=pass` with `header.i=@` your domain, and `dmarc=pass` under `Authentication-Results`.

If the only DKIM pass is for a domain ending in `gappssmtp.com`, DKIM isn't on yet for your domain. If you published a key, go back to [Turn DKIM on](/docs/google-workspace/#turn-dkim-on); if not, start at [Create the key](/docs/google-workspace/#create-the-key).

If you send to people at Gmail in bulk, about 5,000 messages a day or more, Google requires all three records; [what Gmail, Yahoo, Outlook and Apple require of senders](/docs/sender-requirements/) quotes the rules.

## Sources

Google Workspace Admin Help, each updated 10 November 2026 and read on 14 November 2026: [Set up SPF](https://knowledge.workspace.google.com/admin/security/set-up-spf), [Set up DKIM](https://knowledge.workspace.google.com/admin/security/set-up-dkim), [Troubleshoot DKIM issues](https://knowledge.workspace.google.com/admin/security/troubleshoot-dkim-issues), [Set up DMARC](https://knowledge.workspace.google.com/admin/security/set-up-dmarc), [Recommended DMARC rollout](https://knowledge.workspace.google.com/admin/security/recommended-dmarc-rollout) and [About DMARC reports](https://knowledge.workspace.google.com/admin/security/about-dmarc-reports).
