Configuring SPF Records for InMotion Hosting Accounts

Setting up a Sender Policy Framework (SPF) record for your domain hosted with InMotion Hosting tells receiving mail servers which IP addresses are authorized to send email on your behalf. Without a properly configured SPF record, legitimate emails sent from your website or control panel may be marked as spam or rejected entirely by major inbox providers. In this guide, you will learn the exact syntax, step-by-step management procedures, and best practices to ensure your domain's email authentication is completely secure.

To simplify the creation process before you log into your server control panel, you can use the SPF Record Generator to quickly build a valid TXT record tailored to your exact mail-sending infrastructure.

Understanding SPF Records and How They Work

An SPF record is a type of TXT resource record published in your domain's DNS zone. When an incoming mail server receives a message claiming to be from example.com, it performs a DNS lookup to check the domain's SPF policy. If the message originated from an IP address or server authorized within that policy, the check passes. If it originated elsewhere, the message fails authentication and is subjected to spam filtering or outright rejection.

The Anatomy of an SPF Record

An SPF record always begins with the version identifier v=spf1 followed by a series of mechanisms and modifiers that dictate authorization rules. For a standard InMotion Hosting account, your baseline requirement includes referencing the InMotion mail servers alongside your web server's IP address.

Consider this standard example for example.com:

v=spf1 mx ip4:192.0.2.1 include:spf.example.com ~all

• v=spf1: Declares the record as version 1 of the SPF standard.
• mx: Authorizes the mail exchangers defined in your domain's MX records to send mail.
• ip4:192.0.2.1: Specifically authorizes your dedicated or shared server's IPv4 address (using documentation IP 192.0.2.1 as an example).
• include:spf.example.com: Pulls in third-party authorized senders.
• ~all: The softfail mechanism, advising receiving servers to treat unauthorized emails with caution without outright dropping them.

Preparing Your SPF Record for InMotion Hosting

Before you create or modify your DNS entries, you need to gather specific network details about your InMotion Hosting environment. Depending on whether you use shared hosting, a Virtual Private Server (VPS), or a dedicated server, your sending mechanics will vary.

Determining Your Mail Server Details

1. Log into your Account Management Panel (AMP).
2. Locate your server dashboard to find your primary server IP address (e.g., 192.0.2.50).
3. Note your primary domain name hosted on the account.

If you manage multiple third-party services that send mail as your domain—such as newsletter platforms, transactional email APIs, or CRM software—you must gather their specific include statements as well. Consolidating all authorized services into a single SPF record is critical because a domain is only allowed to have one active SPF TXT record.

Step-by-Step InMotion Hosting SPF Record Setup

InMotion Hosting typically relies on cPanel or AMP-managed DNS zones. Follow these menu paths to add your SPF record. Note that exact menu names may differ slightly depending on your specific account tier or control panel version.

Step 1: Access the DNS Zone Editor

1. Log into your InMotion Hosting cPanel or Account Management Panel.
2. Navigate to the Domains or Advanced section and click on Zone Editor (or DNS Manager in older AMP layouts).
3. Locate your target domain (example.com) and click Manage.

Step 2: Check for Existing SPF Records

Look through the existing DNS records for any entry starting with v=spf1. If you find an old or default SPF record, you should edit it rather than creating a duplicate. Having multiple SPF records breaks email authentication entirely.

Step 3: Add the New TXT Record

1. Click the dropdown arrow next to Add Record and select Add TXT Record.
2. In the Name or Zone field, enter your domain name or leave it as @ to represent the root domain (example.com).
3. In the TTL (Time To Live) field, leave the default value or set it to 14400 (4 hours).
4. In the Record, TXT Data, or Value field, paste your generated SPF string.

Example record entry:

Type	Name	TTL	Record / Value
TXT	example.com.	14400	v=spf1 ip4:192.0.2.50 +mx ~all

5. Click Save Record or Add Record to commit the changes to the DNS zone.

Verification and Troubleshooting

Once you save your DNS changes, propagation can take anywhere from a few minutes up to 24 hours globally. You should verify that your record is syntactically correct and publicly visible.

Using Command Line Tools

You can query your domain's TXT records using dig or nslookup in your terminal:

dig example.com TXT

Sample expected output:

;; ANSWER SECTION:
example.com.        3600    IN      TXT     "v=spf1 ip4:192.0.2.50 +mx ~all"

If you are on Windows, open PowerShell and run:

Resolve-DnsName -Name example.com -Type TXT

Common Mistakes and How to Fix Them

• Multiple SPF Records: If your zone contains two or more TXT records beginning with v=spf1, mail servers will return a permanent error (permerror). Combine all authorized services into a single string.
• Exceeding the DNS Lookup Limit: The SPF specification imposes a strict limit of 10 DNS lookup mechanisms (using include, a, mx, ptr, etc.). Exceeding this causes authentication to fail. Use IP blocks (ip4: or ip6:) instead of nested includes where possible.
• Incorrect Syntax: Typos in mechanism names (e.g., writing ip4-address instead of ip4:) invalidate the record.

Checklist for Successful SPF Deployment

• Gathered all IP addresses and third-party email service include statements.
• Verified that only one SPF TXT record exists on the root domain.
• Successfully added the record via the InMotion Hosting DNS/Zone Editor.
• Tested DNS propagation using dig or PowerShell.
• Sent a test email to an external mailbox and inspected headers for Received-SPF: Pass.