Connect your domain on Namecheap
Namecheap splits MX away from the other records — the most common reason a Namecheap setup looks complete but isn't.
Namecheap adds your domain to whatever you type
Enter names without your domain — _mailflat-verify, not _mailflat-verify.acme.com. Typing the full name stores it as _mailflat-verify.acme.com.acme.com, and no amount of waiting will make that verify. In the dashboard, keep the Provider dropdown on name only and use the copy button next to each Host.
Where the DNS editor is
- Log in to Namecheap
- Domain List → Manage
- Advanced DNS
- Add New Record
Field names here: Host for the record name, Value for the value, (unlabelled column after Value) for MX priority.
The five records, as Namecheap wants them
Your real values are on Domains in the dashboard — the verification token and the DKIM key are unique to your domain. Everything else looks exactly like this.
| Type | Host | Value | What it does |
|---|---|---|---|
| TXT | _mailflat-verify | mf-verify-… (yours is in the dashboard) | Proves you own the domain. Verification fails without it. |
| MX | @ | mail.mailflat.net.Priority 10 — (unlabelled column after Value) | Routes incoming mail to MailFlat. |
| TXT | @ | v=spf1 include:mailflat.net ~all | Authorises MailFlat to send for your domain. |
| TXT | mail._domainkey | v=DKIM1; k=rsa; p=… (yours is in the dashboard) | Signs your outgoing mail. |
| TXT | _dmarc | v=DMARC1; p=none; | Tells receivers what to do when a check fails. |
Namecheap specifics
Namecheap adds your domain for you. The Host field takes @, _mailflat-verify, mail._domainkey, _dmarc — never the full name.
MX is not in Host Records. Scroll to Mail Settings, switch the dropdown to Custom MX, and add it there. Until you do that, the MX box simply isn't shown and mail cannot arrive.
The Priority field has no header — it is the narrow column right after Value.
TTL: Automatic is fine.
Then verify
Back on Domains, press Verify. If it fails, the message says what is actually wrong — including the case where your records landed one level too deep, with the exact name we found them under. DNS changes are usually visible within minutes; a failure that names a wrong record will not fix itself by waiting.
More on custom domains: Custom domains (BYOD).