DNS Checker
Diagnose a domain's DKIM, SPF, DMARC, return-path and MX records before sending.
Taifa Mail inspects a domain's DKIM, SPF, DMARC, bounce-routing and MX records and tells you whether they are configured correctly. Use it to diagnose deliverability issues or confirm your setup before verifying a domain.
Where to find it
Open a domain from the Domains page. The domain detail view runs the DNS checks against your live DNS and shows the result for each record. The checks always run against a domain you have already added to Taifa Mail.
Domain Health
The Domain Health check returns one verdict and a plain-language recommendation per record. It covers five checks:
| Check | What it means |
|---|---|
| DKIM signature | The DKIM TXT record is publishing, so your mail can be cryptographically signed. |
| SPF | The SPF TXT record is publishing, so receivers can confirm Taifa Mail is an authorised sender. |
| DMARC | A DMARC record is published. The check also reports the policy strength (none, quarantine, reject). |
| Bounce routing | The taifa-bounce CNAME is publishing, so bounce and complaint feedback routes back to Taifa Mail. |
| MX (inbound mail) | Whether the domain has an MX record and where inbound mail routes. |
Each check returns one of four states:
- ok -- the record is correct.
- warn -- the record is missing or weak but not blocking sending. For example, a missing bounce CNAME, a missing MX record, or DMARC still at
p=none. - error -- a required record (DKIM, SPF, DMARC) is not publishing.
- info -- informational only. For example, inbound mail routes to another provider, which is fine if you only send.
Where a record needs fixing, the check includes the exact record type, host and value to publish.
MX status
A dedicated MX status check reports whether the domain's MX record routes mail to Taifa Mail. This is the check the app runs before it lets you create an email forward. It returns the current MX records and whether any of them point to Taifa Mail.
Diagnose
The diagnose check looks up the domain in public DNS, lists any detected issues, and returns a health score. The score is based on how many of the domain's records are verified, with a penalty for each detected issue.
Common uses
- Before domain verification. Run the checks after adding your DNS records to confirm they are visible before clicking Verify.
- Debugging deliverability. If your emails are landing in spam, check whether DKIM, SPF, or DMARC records are missing or broken.
- Before setting up forwarding. Use the MX status check to confirm the domain can receive mail.
DNS changes can take time to propagate. If a check shows an error right after you added a record, wait 15 to 30 minutes and check again.