---
title: "Email Authentication (DKIM Configuration)"
slug: "email-authentication-dkim-configuration"
updated: 2026-04-09T21:52:35Z
published: 2026-04-09T21:52:35Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Authentication (DKIM Configuration)

**DKIM (DomainKeys Identified Mail)** authenticates the email you send from Slate. It lets email servers know that an email is actually from you and not from a spammer. This improves deliverability and makes your email less likely to be caught in spam filters. It also removes the *Sent via* label in Gmail and other email clients.

DKIM requires your IT group to add a small entry to the DNS record for your domain. A DNS record matches hostnames (a friendly name like `www.google.com`) to the actual IP address of a server on the internet (for example, `172.217.2.206`).

We have a DKIM tool to help you set this up. It involves creating a DKIM configuration and sharing it with your IT group. Once they have updated the DNS records, select a *validate* link for DKIM to take effect.

## Setting up DKIM for outgoing Slate emails

1. Go to **Database** → **DKIM Configuration**.
2. Enter your email domain.
3. Select **Lookup**.
4. If this is the first time you have set up DKIM, the status *Inactive / Awaiting Configuration* appears.
5. Select **Create Configuration**. The email domain follows the `@` in the email address you use for emails sent from Slate. It defaults to your school’s domain name, like `slateuniversity.edu`.
6. Enter a **subdomain**. Leave this as the default, `slate-mx`, unless IT notifies you that this subdomain is already in use.
7. Select **Save.**
8. Share these details with your IT group, specifically those responsible for DNS records. They must update your institution’s DNS records with these values.
9. Once your IT group has added these records, return to your DKIM page.
10. Select **Validate Configuration**.

Once the configuration has been validated, Slate uses DKIM with any emails sent from Slate.

If IT notifies you that this subdomain is already in use and you've already begun the set-up, you can delete the existing configuration and once again follow the steps in this section, and instead entering a new subdomain value.

## Validate DKIM configuration

1. Go to **Database** → **DKIM Configuration**.
2. Enter your email domain.
3. Select **Lookup**.
4. Select **Validate Configuration**.
5. If all three DNS records appear in **black**, your DKIM configuration is valid. **Red** **text**domains are not yet valid. Have IT ensure the appropriate DNS records are published.

## Setting up DKIM for additional email domains

Slate supports DKIM configuration for multiple domains should you send an email from Slate on behalf of various subdomains.

By default, Slate will allow you to add DKIM configuration for any subdomain that falls under your Slate database domain. For example, if your database domain is `apply.undergrad.slateuniversity.edu`, you can create DKIM configuration for `students.undergrad.slateuniversity.edu`. You will not be able to create a DKIM configuration for `students.graduate.slateuniversity.edu`, however, since this domain is not part of your Slate instance domain.

To add domains like these to the *Allowed Service Domains*list:

1. Go to **Database** → **Configuration Keys**.
2. Select **Allowed Service Domains List**.
3. Enter email domains as a comma-separated list. For example, `students.graduate.slateuniversity.edu,alumni.graduate.slateuniversity.edu`.
4. Select **Save.**Allow 15-20 minutes for this updated configuration key to propagate to all web servers.
5. Go to **Database**→ **DKIM Configuration.**
6. [Configure the new domain](/v1/docs/email-authentication-dkim-configuration#setting-up-dkim-for-outgoing-slate-emails).

> [!WARNING]
> 📝 Note
> 
> If you receive an error message when attempting DKIM validation for additional domains or subdomains, please [create a ticket with the Support Desk](/v1/docs/support-resources#how-do-i-submit-a-ticket). A member of our team will need to complete the validation process on your behalf.