FindLeadEmails
Email intelligence
Try it for free
DNS host · DKIM

DKIM record for Amazon Route 53

How to add a DKIM record when DNS or mail is at Amazon Route 53. Real steps, then a live lookup.

Hosted zone must be the one the domain's NS records actually use.

  1. Create record for selector._domainkey, type TXT or CNAME as instructed. Quote TXT values.

Official docs: Amazon Route 53. Other records for this provider: SPF · DKIM · DMARC

Does this page apply to you?

Run this first. Amazon Route 53 only matters if it is where your DNS or mail actually lives.

dig +short NS yourdomain.com

Expect: Names like ns-123.awsdns-45.com. They must match the public hosted zone you are editing; a private hosted zone is invisible to the internet.

Specific to Amazon Route 53

  • Each string inside a TXT value is limited to 255 characters, and a 2048-bit DKIM key is longer than that. Split it into several quoted strings in the same value: "v=DKIM1; k=rsa; p=MIIB…" "…rest of key".
  • The record name is selector._domainkey. Route 53 appends the zone name.
  • For a CNAME-style DKIM record, create a CNAME in the same zone with the same name rule.

What you should end up with

Illustrative values. Use the exact host and value your provider shows you where it generates them.

Type  Name  Value
TXT  google._domainkey  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A…" "…second part of the key"

What the receiving server does with this record

Your sending server signs each message with a private key and adds a DKIM-Signature header naming the signing domain (d=) and the selector (s=). The receiver builds the hostname s._domainkey.d, fetches the public key from DNS, and verifies the signature. A valid signature proves the message came from that domain and was not changed on the way.

Mistakes that break it

  • Published, but signing never switched on. Most providers need a second step after the DNS record exists. Until then they sign with their own domain, which passes DKIM but does not align with your From address, so it does nothing for DMARC.
  • A doubled hostname. Typing the full name into a field that already appends your domain gives selector._domainkey.yourdomain.com.yourdomain.com.
  • A damaged key. A 2048-bit key is longer than one 255-character DNS string. Stray spaces, line breaks and silent truncation all invalidate it.
  • The wrong selector. The record is published under one name and the sender signs with another.

Check it from the command line

The final test is a real message: send one to a Gmail address, open Show original, and read the DKIM line. Before that, confirm the record resolves:

dig +short TXT google._domainkey.yourdomain.com

Check it live

Check the DKIM record

Look up the live DNS after you save. This tool does not spend credits.

Related