Email DNS configuration checker
Updated
Enter a domain to run all the DNS checks that matter for sending email at once.
Looks up public DNS only. Nothing you enter is stored.
What it checks
| Check | Looks for |
|---|---|
| SPF | One record, under 10 DNS lookups, a sensible ending, no +all or ptr |
| DMARC | A valid policy, reporting address, and the rollout percentage |
| MX | Mail servers that resolve to real addresses, with a backup |
| DKIM | A published key on 14 common selectors, and key strength |
Each section opens into the same detailed findings as the individual SPF, DKIM, DMARC and MX tools.
Reading the summary
- Errors are things that will cause failures, such as two SPF records or no DMARC record. Fix these first.
- Warnings are weaker settings, such as
p=noneDMARC. They work, but they leave you exposed. - No DKIM found often just means a custom selector. Look up the selector in the
DKIM-Signatureheader of a message you sent, then use the DKIM tool.
What to do next
If you send application email, verify your sending domain with your provider and add the records it gives you. Then re-run this check. For the reasoning behind each record, read SPF, DKIM and DMARC explained. If mail is already landing in spam, follow the debugging guide.
Frequently asked questions
- Why does it only check common DKIM selectors?
- A DKIM selector can be any name your provider chose, and DNS cannot be listed to discover them. The scan tries 14 common ones. If none is found, use the DKIM checker with the selector from a real message header.
- Does a clean result mean my email will reach the inbox?
- No. It means the DNS records are in order. Inbox placement also depends on reputation, content and recipient behaviour.
Need reliable email delivery? Try Inboxili
Create a workspace, verify a domain, and make your first API call.