Add Meisa's DNS records at Cloudflare, GoDaddy, Namecheap or Route 53
Add the 3 DKIM CNAMEs, SPF and DMARC records where your domain's DNS is managed. On Cloudflare set CNAMEs to DNS only; elsewhere drop the domain from the name.
On this page
Add the 5 records from Meisa at the company that hosts your domain’s DNS. The two mistakes that block most verifications: on Cloudflare, the DKIM CNAMEs must be set to DNS only (grey cloud), and at GoDaddy and Namecheap you must remove your domain from the end of the record name, because they add it for you.
Before you start
- In Meisa, open Email setup and find your domain’s records (the Verify your domain step, or View records next to the domain).
- Keep that tab open. You will copy each Name and Value with the copy icons.
- Not sure where your DNS is hosted? It is usually where you bought the domain, unless you moved your nameservers to Cloudflare or Route 53. A free “NS lookup” tool shows your nameservers.
Meisa shows names in full, for example abc123._domainkey.northwind.app. The examples below use northwind.app. Replace it with your domain and use your real tokens from Meisa.
How to write the name at each host
| Meisa shows | Cloudflare and Route 53 | GoDaddy and Namecheap |
|---|---|---|
abc123._domainkey.northwind.app |
paste as is, or abc123._domainkey |
abc123._domainkey |
@ (SPF) |
@ (Cloudflare) or leave empty (Route 53) |
@ |
_dmarc |
_dmarc |
_dmarc |
Cloudflare
- Log in to Cloudflare and click your domain.
- In the left menu, click DNS, then Records.
- Click Add record.
- For each DKIM record: Type
CNAME, Name the DKIM name from Meisa, Target the value from Meisa (ends in.dkim.amazonses.com). - Click the orange cloud so Proxy status shows DNS only (grey cloud). This is required: a proxied CNAME hides the record from AWS and the domain never verifies.
- Click Save. Repeat for the other two DKIM records.
- For SPF: Type
TXT, Name@, Contentv=spf1 include:amazonses.com ~all. If a TXT record starting withv=spf1already exists on@, edit that one instead and addinclude:amazonses.combefore~all. - For DMARC: Type
TXT, Name_dmarc, Contentv=DMARC1; p=none;. Skip this if_dmarcalready has a DMARC record.
GoDaddy
- Log in to GoDaddy and open your domain portfolio.
- Click your domain, then DNS (some accounts show Manage DNS).
- Click Add New Record.
- For each DKIM record: Type
CNAME, Name only the part before your domain, for exampleabc123._domainkey, Value the value from Meisa. Leave TTL at the default. Click Save. - For SPF: Type
TXT, Name@, Valuev=spf1 include:amazonses.com ~all. If an SPF record already exists, edit it instead. - For DMARC: Type
TXT, Name_dmarc, Valuev=DMARC1; p=none;.
If you paste the full name, GoDaddy creates abc123._domainkey.northwind.app.northwind.app and the record is never found.
Namecheap
- Log in to Namecheap and go to Domain List.
- Click Manage next to your domain, then open the Advanced DNS tab.
- Under Host Records, click Add New Record.
- For each DKIM record: choose CNAME Record, Host
abc123._domainkey(without your domain), Target the value from Meisa. Click the green check to save. - For SPF: choose TXT Record, Host
@, Valuev=spf1 include:amazonses.com ~all. Edit the existing SPF record if there is one. - For DMARC: choose TXT Record, Host
_dmarc, Valuev=DMARC1; p=none;.
If your domain uses Namecheap’s email forwarding or another mail service, keep their SPF entries and just add include:amazonses.com.
Amazon Route 53
- In the AWS console, open Route 53, then Hosted zones, and click your domain.
- Click Create record.
- For each DKIM record: in Record name, type only the part before your domain (
abc123._domainkey). The domain is already shown after the box. Record typeCNAME, Value the value from Meisa. Click Create records. - For SPF: leave Record name empty, Record type
TXT, Value"v=spf1 include:amazonses.com ~all"with the double quotes. If a TXT record already exists on the root, edit it and add the SPF line on its own line instead. - For DMARC: Record name
_dmarc, Record typeTXT, Value"v=DMARC1; p=none;".
Check the records
Go back to Meisa and click Check my records. Most hosts publish changes within minutes, but it can take up to an hour. While the page is open, Meisa checks again every 2 minutes. Each row turns to Found when it is live.
Troubleshooting
- DKIM stays “Not found yet” on Cloudflare: the CNAME is proxied. Switch it to DNS only.
- Name doubled: at GoDaddy or Namecheap, remove your domain from the end of the name.
- Two SPF records: a domain may only have one
v=spf1record. Merge them into one. - Records added at the wrong place: if your nameservers point to Cloudflare, records added at your registrar do nothing. Add them where your nameservers point.
- More help: My domain is still pending verification.
Related articles
Did this answer your question?
Thanks for letting us know.Thanks, we will improve this article. Want a hand right now?
Still need help?
Chat with us and get an answer in a few minutes.