Namecheap's Advanced DNS editor can publish email records when its nameservers are authoritative for the domain. For a Free Domain Mail catch-all inbox you need two: a TXT ownership record and an MX record pointing to mx.freedomainmail.com.
Back up the current zone
Open Domain List > Manage > Advanced DNS and copy existing MX and TXT values before editing.
If the domain uses custom nameservers, make the change at that external DNS provider instead.
Add the catch-all records
Free Domain Mail turns the domain into a receive-only catch-all inbox: every address receives mail, there is nothing to create per address, and messages are kept for 30 days. It never sends or forwards mail.
Add a TXT record with Host _maildock-verify and the maildock-verify=… value shown in the app. The app shows the exact host and value: at providers that append the domain automatically, enter only _maildock-verify; at providers that want the full name, use _maildock-verify.yourdomain.com. Before adding the MX record, choose Custom MX under Mail Settings on the Advanced DNS page; then add an MX record with Host @, mail server mx.freedomainmail.com and priority 10, entered in separate fields. Remove any other MX records for the domain so all incoming mail reaches one place.
The MX records decide where all incoming mail for the domain goes. If the domain already receives mail you depend on, such as a work mailbox, connect a different domain instead.
Type Name / Host Value Priority
TXT _maildock-verify maildock-verify=… (shown in the app) —
MX @ mx.freedomainmail.com 10SPF, DKIM and DMARC: only if this domain also sends mail
Free Domain Mail never sends, so these records are only needed if this domain also sends mail through another provider.
Use @ for the root SPF record and keep only one v=spf1 record. For DKIM, copy the selector hostname and TXT or CNAME target exactly. Publish DMARC as TXT at _dmarc, start at p=none with a reporting address you control, then stage enforcement after reviewing senders.
Check public DNS and real delivery
Use the DNS Checker after saving and allow for TTL caches. The MX answer should list only mx.freedomainmail.com.
Send a test message from an outside account to a new name at the domain and confirm it arrives in the inbox.
Common mistakes to avoid
- Leaving an old MX record next to mx.freedomainmail.com.
- Deleting unrelated Namecheap verification records.
- Editing Namecheap while external nameservers are active.
Frequently asked questions
What Host should I use for the MX and TXT records?
The MX record uses @, which means the root of the domain in Namecheap Advanced DNS. The ownership TXT record uses _maildock-verify as its Host, exactly as the app shows it.
Why is my new record not visible?
Confirm authoritative nameservers, record host formatting and the previous TTL before republishing it.
Do I need SPF for a receive-only inbox?
No. SPF lists services allowed to send for the domain. Add it only if the domain also sends mail through another provider.