include reference to your existing SPF record. MailChannels maintains its own SPF record, so it always reflects the current sending addresses — you don’t need to update anything when IPs change.
Required DNS records
You need two DNS records for full SPF coverage with MailChannels.SPF record (for your sending domain)
Add or update the TXT record for your domain:| Location | Type | Value |
|---|---|---|
example.com | TXT | v=spf1 a mx include:relay.mailchannels.net ~all |
example.com with your actual domain name.
If you already have an SPF record, add include:relay.mailchannels.net to it — do not create a second SPF record. Only one SPF TXT record is permitted per domain. Place the include before the all mechanism, since all always matches and must appear at the end.
Example — adding MailChannels to an existing SPF record:
Before
After
Domain Lockdown record (strongly recommended)
| Location | Type | Value |
|---|---|---|
_mailchannels.example.com | TXT | v=mc1 auth=<your-account-id> |
<your-account-id> with the Account ID shown in your Host Console. This record tells MailChannels that only your account is authorized to send from your domain, locking out any other MailChannels account from spoofing it.
If you cannot configure Domain Lockdown right away, you can use a neutral qualifier as a temporary measure:
? qualifier produces a neutral SPF result. This allows messages from MailChannels to be accepted by hosts that would otherwise reject on SPF failure, but it does not help with DMARC alignment (which will depend on DKIM only until Domain Lockdown is configured).
Verify your SPF record
After updating your DNS, confirm the record is correct usingdig or nslookup:
include:relay.mailchannels.net entry.
To verify the Domain Lockdown record:
DNS changes can take up to 48 hours to propagate, though most resolvers pick up changes within minutes to a few hours.
Common SPF mistakes
Creating two SPF records for the same domain — Only onev=spf1 TXT record is allowed per domain. If you add a second one, both records become invalid. Edit your existing record instead of creating a new one.
Placing include:relay.mailchannels.net after all — The all mechanism matches everything, so any mechanisms after it are ignored. Always put include statements before the all at the end.
Exceeding the 10 DNS lookup limit — SPF records are limited to 10 DNS lookups during evaluation. If you have many include statements, you may hit this limit. Use an SPF flattening tool to consolidate lookups if needed.
Using -all (hard fail) without testing first — A -all suffix causes receiving servers to reject messages that don’t match. A ~all (soft fail) is safer during initial setup because it marks non-matching messages rather than rejecting them outright. Switch to -all once you are confident your record is complete.
cPanel bulk SPF setup
If you manage many domains in cPanel, you can add SPF records in bulk using thespf_installer script from the command line:
The spf_installer is a built-in cPanel/WHM script that lets system administrators add or update SPF.
cPanel Documentation
Next step
Once your SPF records are in place, configure your mail server to relay through MailChannels:Configure your mail server
Set up your MTA to use MailChannels as a smart host for outbound delivery.

