Mail DNS and deliverability
The exact MX, SPF, DMARC, DKIM and autodiscover records for business email, and how to fix mail that lands in spam.
Inbound mail depends on MX. Outbound trust depends on SPF, DKIM and DMARC. Get all four right and most deliverability problems disappear.
Required records
| Type | Name | Value |
|---|---|---|
| MX | @ |
10 mx.webspeed.online |
| TXT | @ |
v=spf1 include:spf-c.mailbaby.net ~all |
| TXT | _dmarc |
v=DMARC1; p=none; rua=mailto:[email protected]; fo=1 |
| TXT | <selector>._domainkey |
The DKIM public key, starting v=DKIM1; |
| CNAME | autodiscover |
mail.webspeed.online |
| CNAME | autoconfig |
mail.webspeed.online |
| SRV | _imaps._tcp |
0 1 993 mail.webspeed.online |
| SRV | _submissions._tcp |
0 1 465 mail.webspeed.online |
Copy the DKIM value exactly as the console shows it. Do not reformat or wrap the key; a single missing character invalidates the signature.
The _dmarc value above is the default with policy none. If you chose quarantine or reject in the console, use that policy instead.
Publish them automatically
If the zone is on Zoophost nameservers, the console can write the records:
- Open the mail domain → DNS records.
- Choose Publish to our nameservers.
Re-running it replaces the record sets rather than duplicating them.
From the DNS zone editor, Mail records does the same for a zone, with options for the DMARC policy, an SPF include for the mail host, and an optional DKIM selector and key.
Publish them manually
If DNS is at another provider, create each record by hand. Notes:
- Names: use
@for the naked domain; enter the selector as shown, for examplezoop._domainkey. - TTL: 3600 is fine.
- Cloudflare: set mail-related records to DNS only, not proxied. Proxying does not forward port 25 and terminates IMAP/SMTP at Cloudflare's edge, so mail stops working.
- MX priority: keep
10unless you run a second mail host.
Check deliverability
Console → the mail domain → Deliverability → Run check.
It resolves MX, SPF, DMARC, DKIM selectors and nameservers, and reports:
- delivered to us — the record points at the mail host
- points elsewhere — another provider answers
- missing — no record found
- allows our relay — SPF includes the sending relay
- no relay include — SPF exists but does not include it
Fix reported problems in order: MX first (inbound), then SPF, then DKIM, then DMARC.
Why mail lands in spam
Work through this list in order:
- SPF is missing or does not include the relay. The check will say so.
- DKIM is missing or the key does not match. A mismatched key is worse than no key.
- DMARC policy is
noneand the domain is new. Reputation is built over time;quarantineafter SPF and DKIM pass consistently. - The From domain does not match the sending domain. Send as your own domain, not a free-mail address.
- Links or attachments look like phishing. Shorteners, mismatched link text and attachments from unknown senders all raise the score.
- The recipient uses an aggressive filter. Check the bounce or spam report; it names the reason more often than people expect.
What the daily sending limit covers
Each mailbox has a daily sending allowance. It is enforced for mail sent through the console and API. Mail sent from a mail client or webmail bypasses that counter.
If you need bulk transactional mail, do not route it through a mailbox. Ask support about a dedicated sending setup.
Common problems
Inbound mail missing — MX is absent, proxied, or points elsewhere. Check with dig MX yourdomain.com.
Outbound rejected with “SPF fail” — the SPF record is missing or has more than one v=spf1 record. Merge them into one.
DKIM fails after a provider change — the selector in DNS no longer matches the key the server signs with. Republish from the console.
Mail works for some recipients only — that is reputation, not DNS. Check DMARC reports and the recipient's rejection message.
Autodiscover fails in Outlook — the autodiscover CNAME is missing or proxied. Add it as DNS-only.
Next
- spf
- dkim
- dmarc
- mx
- autodiscover
- deliverability
- spam
- dns
Ready to use this
Mailboxes on your own domain with webmail and IMAP.
- MX, SPF, DKIM and DMARC published for you
- Daily sending caps that protect delivery

