Mailfully logo

Namecheap DNS

Namecheap keeps everything on the Advanced DNS tab and adds one record type at a time. Here is that order for Mailfully.

Namecheap treats MX as a record type of its own, distinct from CNAME and TXT, so the MAIL FROM MX record needs a different Type selection than the SPF record that shares its host. Find acme.com under Domain List, choose Manage, and open the Advanced DNS tab; Add New Record opens a row for each entry below.

Add the records

1
Add the three DKIM CNAMEs

Add a CNAME row for each of the three DKIM tokens:

FieldValue
TypeCNAME Record
Host<token>._domainkey.mail
Value<token>.dkim.amazonses.com
TTLAutomatic

The Host field is relative to acme.com, so drop the trailing .acme.com from the full name Mailfully returned.

2
Add the MAIL FROM MX record
FieldValue
TypeMX Record
Hostsend.mail
Valuefeedback-smtp.us-east-1.amazonses.com
Priority10
TTLAutomatic
3
Add the MAIL FROM SPF record
FieldValue
TypeTXT Record
Hostsend.mail
Valuev=spf1 include:amazonses.com ~all
TTLAutomatic
4
Add the DMARC record
FieldValue
TypeTXT Record
Host_dmarc.mail
Valuev=DMARC1; p=none;
TTLAutomatic

The apex itself uses @ for a Host value; none of Mailfully's six records target the apex, so you won't need it here, but it's the value to reach for if a later record does.

MX gets its own record type

CNAME and TXT carry no priority concept, so Namecheap only exposes the Priority field on MX Record.

Verify

dig +short <token>._domainkey.mail.acme.com CNAME
dig +short send.mail.acme.com MX
dig +short send.mail.acme.com TXT
dig +short _dmarc.mail.acme.com TXT

Verify with dig sets out what each of the four should return.