Authenticate email with DKIM

About DKIM

You can help prevent spoofing by adding a digital signature to outgoing message headers using the DKIM standard. This involves using a private domain key to encrypt your domain's outgoing mail headers, and adding a public version of the key to the domain's DNS records. Recipient servers can then retrieve the public key to decrypt incoming headers and verify that the message really comes from your domain and hasn't been changed along the way.

Google Apps' digital signature conforms to the DomainKeys Identified Mail (DKIM) standard.

How DKIM works

To add a digital signature to outgoing mail, you generate a 1024-bit domain key that Google Apps uses to create signed mail headers that are unique to your domain. You add the public key to the Domain Name System (DNS) records for your domain. Recipients can then verify the source of a mail message by retrieving your public key and using it to confirm your signature.

Overview of steps

Repeat these steps for each domain associated with your Google Apps account.

  1. Generate the public domain key for your domain.
  2. Add the key to your domain's DNS records so recipients can retrieve it for reading the DKIM header.
  3. Turn on email signing to begin adding the DKIM header to outgoing mail messages.

Skip the first 2 steps if you purchased your domain from one of our domain host partners while signing up for Google Apps. Google automatically generates the domain key and adds the necessary DNS record when you turn on authentication.

Next: Generate the domain key

Our domain already has a DKIM key

If you already have a DKIM domain key for your domain—for example, if your legacy mail server signs outgoing mail—you still need to generate a separate key for Google Apps to use. The Google Apps domain key is distinguished from any other key by a string known as a selector prefix. The selector prefix for the Google Apps domain key is "google" by default, but you can enter a new selector prefix when you generate the key.

Using an outbound mail server

If you use an outbound mail gateway that modifies outgoing messages, such as adding a compliance footer, the change invalidates the DKIM signature. You need to prevent the gateway server from modifying messages or have the gateway server subsequently DKIM sign the messages.

For other anti-spoofing measures available through Google, see SPF records and Understanding DMARC.
Was this article helpful?
Sign in to your account

Get account-specific help by signing in with your Apps for Work account email address, or learn how to get started with Apps for Work.