If you use a third-party email service, application, or mail server to send emails from your domain, you may need to update your SPF record to authorise its IP address.
Although updating DNS records is a technical task, following the steps below carefully will help ensure your email continues to be delivered successfully.
This guide will help you safely add an IP address to your domain’s SPF (Sender Policy Framework) record using cPanel.
By the end of this guide, you’ll know how to update your SPF record without creating duplicate records or affecting your existing email services.
What This Means
SPF (Sender Policy Framework) is an email authentication method that tells receiving mail servers which servers and IP addresses are allowed to send email on behalf of your domain.
When an email is received, the recipient’s mail server checks your SPF record to verify that the sending server is authorised.
Adding the correct IP addresses helps:
- Improve email deliverability
- Reduce spoofing and phishing attempts
- Protect your domain’s reputation
- Reduce the likelihood of emails being marked as spam
Important:
You should update your SPF record whenever you begin sending email from a new server, application, or third-party service.
Examples include:
- A VPS or dedicated mail server
- CRM platforms
- Marketing email platforms
- Business applications that send email from your domain
Understanding SPF Record Elements
A typical SPF record may look like this:
v=spf1 ip4:123.123.123.123 include:_spf.example.com ~all Each element has a specific purpose.
v=spf1 – Identifies the TXT record as an SPF record.
ip4: – Authorises a specific IPv4 address to send email on behalf of your domain.
include: – Imports SPF rules from another authorised mail provider. This is commonly used when your email is hosted by a third-party provider.
~all – Soft Fail. Unauthorised senders are marked as suspicious but are not automatically rejected. This is recommended for most domains.
-all – Hard Fail. Unauthorised email is rejected outright. This setting should only be used once you are confident that every legitimate sending service has been added to your SPF record.
Steps to Check/Edit Your SPF Record via Zone Editor
Step 1: Log in to cPanel
- Sign in to your 1-grid Customer Zone.
- Open the hosting service associated with your domain.
- Launch cPanel.
- Select Zone Editor.
Step 2: Open Your Domain’s DNS Zone
- Locate the domain you want to update.
- Click Manage.
- Locate the TXT record that begins with:
v=spf1 - This is your existing SPF record.
Important:
Your domain should only have one SPF record. Creating multiple SPF records can cause email authentication failures.
Step 3: Edit the Existing SPF Record
- Click Edit beside the SPF TXT record.
- Locate the Record or Value field.
- This contains your existing SPF policy.
Step 4: Add the New IP Address
ip4:123.123.123.123 For example:
v=spf1 ip4:123.123.123.123 include:_spf.example.com ~all Replace the example IP address with your own server’s public IPv4 address.
Step 5: Add Multiple IP Addresses (Optional)
If more than one server sends email for your domain, add each IP address separately.
Example:
v=spf1 ip4:123.123.123.123 ip4:111.111.111.111 include:_spf.example.com ~all Separate each entry with a single space.
Step 6: Save the Record
After reviewing your changes:
- Click Save Record.
- Wait for DNS changes to begin propagating.
Important:
During this period, email authentication behaviour may vary depending on which DNS servers recipients use.
Most DNS updates begin taking effect within approximately 15 minutes, although full propagation can take up to 24 hours.
Important Things to Know
- Your domain should only ever have one SPF record.
- Adding a new SPF record instead of editing the existing one can break email authentication.
- Every email service that sends mail from your domain must be included in your SPF policy.
- DNS changes are not immediate and can take up to 24 hours to propagate globally.
- SPF alone does not prevent spoofing; it works best alongside DKIM and DMARC.
- SPF records have a maximum limit of 10 DNS lookups. Exceeding this limit can invalidate the record.
Before You Move On
Before testing your updated SPF record, make sure you have:
- Saved the DNS record successfully
- Verified that no duplicate SPF records exist
- Allowed sufficient time for DNS propagation
- Sent a test email after propagation completes
If you use multiple email providers or applications, ensure each one is included in your SPF policy.
Common Mistakes to Avoid
- Creating a second SPF record instead of editing the existing one.
- Forgetting to include an existing email provider when updating the record.
- Entering an incorrect IP address when updating the record.
- Removing existing include statements accidentally before saving the record.
- Testing email delivery before DNS changes have fully propagated.
If This Didn’t Work
If email authentication still fails after updating your SPF record, gather the following information before contacting support:
- Your domain name
- The updated SPF record
- The IP address you attempted to add
- Any email delivery or bounce-back messages
- A screenshot of the DNS record in cPanel (if applicable)
- The name of the third-party email service or application you are using
This information will help our team troubleshoot your configuration more efficiently.
Related Articles
- What Is an SPF Record and Why It Matters in DNS for Email
- How SPF and DKIM Improve Email Delivery
- Understanding DNS Records and How to Check These
- Troubleshooting Email Delivery Issues
FAQs
Why do I need to add an IP address to my SPF record?
If another server or application sends email using your domain, it must be authorised in your SPF record. Otherwise, recipients may treat those emails as suspicious or spam.
Can I have more than one SPF record?
No. A domain should only have one SPF record. If multiple SPF records exist, email authentication can fail.
How long does an SPF update take?
Most changes begin propagating within about 15 minutes, but global DNS propagation may take up to 24 hours.
Will updating my SPF record interrupt email?
Provided that the existing record is edited correctly and all authorised sending services remain included, then no.
What happens if I remove an authorised server?
Email sent from that server may fail SPF checks and could be rejected or delivered to spam folders.
Should I use SPF on its own?
SPF provides important protection, but it works best when combined with DKIM and DMARC to improve email authentication and domain security.
Empowering Insight
Email authentication is one of the most effective ways to improve email deliverability. Maintaining an accurate SPF record helps protect your domain’s reputation and reduces the likelihood of legitimate emails being treated as spam.
Need Additional Support?
If you’ve worked through the steps above and are still experiencing email authentication or delivery issues, first review the related articles to confirm your SPF configuration and explore our other email-related articles.
If you still need assistance, contact us with your domain name, current SPF record, and any relevant error messages so our Support Team can help investigate further.