Prerequisites
Before you begin, make sure you have:- A SendKit account with a domain added
- Access to your AWS Management Console
- Your domain’s DNS records from the SendKit domain detail page
Add DNS records
Log in to the AWS Console, go to Route 53 > Hosted zones, and select your domain. Click Create record for each of the following.1. DKIM record
Set the value
In the Value field, paste the DKIM value from SendKit wrapped in double quotes. For example:
"v=DKIM1; k=rsa; p=...".| Route 53 field | SendKit value |
|---|---|
| Record name | sendkit._domainkey |
| Record type | TXT |
| Value | "your DKIM value from SendKit" (with quotes) |
| TTL | 3600 |
2. SPF record
| Route 53 field | SendKit value |
|---|---|
| Record name | send |
| Record type | TXT |
| Value | "your SPF value from SendKit" (with quotes) |
| TTL | 3600 |
3. MX record
In Route 53, MX records combine the priority and value in one field. Enter
10 followed by a space, then the MX value from SendKit.| Route 53 field | SendKit value |
|---|---|
| Record name | send |
| Record type | MX |
| Value | 10 your-mx-value-from-sendkit |
| TTL | 3600 |
4. DMARC record (optional)
Verify your domain
Go back to your SendKit domain detail page and click Refresh. Route 53 DNS changes typically propagate within 60 seconds.If verification doesn’t succeed immediately, wait a minute and try again. SendKit also checks automatically in the background.
Troubleshooting
TXT record not being detected
TXT record not being detected
Make sure your TXT values are wrapped in double quotes. Route 53 requires this for TXT records. Check the record in the console — the value should show with quotes.
MX record format
MX record format
Route 53 combines priority and value in a single field. Enter
10 your-mx-value — not just the hostname. The 10 is the priority.Hosted zone not found
Hosted zone not found
Make sure your domain’s nameservers point to Route 53. If you registered the domain elsewhere, you need to update the nameservers at your registrar to the ones shown in Route 53.

