Skip to main content
Email Deliverability checks the DNS records that authenticate mail from your domain — SPF, DKIM, and DMARC — and tells you which ones are missing, broken, or pointing at the wrong values. When mail from your domain lands in spam folders or gets rejected outright, this is the first place to look. Open it from cPanel home → Email → Email Deliverability.
Email Deliverability listing domains with Valid or Repair status

Email Deliverability with status per domain

​
What it checks

Each domain you host gets its own row with a status: Valid, Problems Exist, or Repair. The three records cPanel inspects: DMARC isn’t auto-checked here but is closely related. cPanel doesn’t manage DMARC; you set it manually as a TXT record (_dmarc.yourdomain.com).

​
Fix what’s broken

When a record shows as broken, click Manage on the domain row to see what cPanel thinks the record should be versus what it currently is. Two paths:
1

If your DNS is hosted with us

Click Repair. cPanel updates the DNS record to the correct value automatically. Propagation is usually instant for our DNS, occasionally up to a few minutes.
2

If your DNS is hosted elsewhere (Cloudflare, etc.)

cPanel can’t edit external DNS. Copy the suggested record value from the Manage page and paste it into your external DNS provider’s TXT record editor.Wait for propagation (up to an hour usually, occasionally longer), then re-run the check.

​
MailChannels TXT record (Noxity-specific)

Outgoing mail on Noxity routes through MailChannels. Two records work together:
  • SPF must include relay.mailchannels.net. Email Deliverability handles this if you click Repair, but verify it ends up in your final SPF.
  • _mailchannels TXT record confirms you authorized Noxity’s relay. cPanel doesn’t auto-create this one. See Domain Management for the value.
Without both, outgoing mail from your domain is likely to be rejected or routed to spam by Gmail, Outlook, and other major providers.

​
Common pitfalls

DNS only allows one SPF record per domain. If you previously had an SPF and a new one was added, both exist and SPF validation fails.Combine them into one. The SPF should start with v=spf1 and end with ~all or -all, with all include: and ip4: clauses in between.
Could be DMARC. If your DMARC policy says p=reject or p=quarantine and DKIM/SPF aren’t aligning correctly, mail goes to spam or gets rejected. Either fix the alignment or relax DMARC to p=none while debugging.
cPanel compares its internal expectation against what’s resolvable on the live DNS. If you edited the record at Cloudflare or elsewhere and the records look correct but cPanel disagrees, refresh the page after a few minutes. Propagation is usually the cause.

​
Need a hand?

Open a ticket

Best for anything that needs an account check or a config change on our end.

Live chat

Faster for quick questions during business hours.