Business Email on Your Own Domain: Setup and Spam Fixes
A practical guide to creating email addresses on your company domain and setting up the DNS records that decide whether your messages reach the inbox.

An SPF record is a TXT record in your domain’s DNS that lists the servers and services allowed to send email as your domain. To work, your domain needs exactly one SPF record that starts with v=spf1, names every service that sends for you, stays within 10 DNS lookups, and ends with ~all or -all. Most email problems that start right after adding a new tool come from breaking one of those rules.
Our guide to business email on your own domain introduced MX, SPF, DKIM and DMARC. This article goes deep on SPF alone.
An SPF record answers one question for the receiving server: is the server that just handed me this message allowed to send for this domain? SPF stands for Sender Policy Framework, and the current standard is RFC 7208 from the IETF.
What many people miss: SPF does not check the From address readers see. It checks the return-path (MAIL FROM), where bounces go, and the name the sending server announces when it connects (HELO). A spoofed message can pass SPF while faking your From address, which is why DMARC requires the domain that passed to match the From domain. Google’s email sender guidelines require every sender to set up SPF or DKIM, and anyone sending more than 5,000 messages a day to Gmail to set up both, plus DMARC.
An SPF record is read from left to right, and the first term that matches the sending server decides the result. Take this example:
v=spf1 a mx ip4:203.0.113.10 include:_spf.mail-service.example ~all
| Term | What it means |
|---|---|
v=spf1 |
Required version tag; it must come first |
a |
Allow the IP address the domain’s A record points to |
mx |
Allow the servers listed in the domain’s MX records |
ip4: / ip6: |
Allow a specific IP address or range |
include: |
Allow whatever another domain’s SPF record allows; this is how you add third-party services |
exists: |
An advanced mechanism small sites rarely need |
ptr |
Legacy mechanism the standard says should not be published; avoid it |
all |
Matches everything, so it goes last and decides what happens to anyone not listed |
Each mechanism can carry a qualifier that sets the result on a match: + pass, - fail, ~ softfail and ? neutral. With no qualifier the default is +, so a and +a mean the same thing. There is also the redirect= modifier, which hands the whole check to another domain’s record; the standard ignores it if the record contains all.
List every sender first, then build a single line that covers all of them.
v=spf1, add the mechanisms, and finish with ~all, with a single space between terms.A domain that sends from its hosting and from a newsletter tool would look like this:
v=spf1 a mx include:_spf.newsletter.example ~all
Because the standard says so: if the receiver finds more than one record starting with v=spf1 on the same name, the result is a permerror, a permanent error that leaves your domain with no valid SPF at all. This is the single most common SPF mistake.
It usually happens like this. A newsletter tool tells you to “add an SPF record”, so you add a new one next to your host’s:
v=spf1 a mx ~all
v=spf1 include:_spf.newsletter.example ~all
Now the check fails for both. The fix is to merge them into one line and delete the extra record:
v=spf1 a mx include:_spf.newsletter.example ~all
Other TXT records, such as site verification tokens, can coexist; the rule applies only to records starting with v=spf1.
RFC 7208 caps a single SPF check at 10 terms that require a DNS lookup; go over and the result is permerror. The terms that count are include, a, mx, ptr and exists, plus the redirect modifier. ip4, ip6 and all do not count.
The hidden trap is that lookups inside each include count too. If a provider’s record contains three includes of its own, adding it costs four lookups, not one, so a short-looking record can already be over the limit.
The standard adds two smaller limits: “void” lookups that return nothing should be limited to two, and each mx mechanism must not trigger more than 10 address lookups.
Ways to stay under the limit:
include for any service you no longer use. It is the easiest saving and the most often forgotten.a and mx point to the same server, one may be enough. If the server’s address is stable, ip4: does not count as a lookup, but remember to update it when the server changes.Use ~all until you are sure the record lists every sender, then move to -all, ideally once DKIM and DMARC are also in place.
| Ending | Result | In practice |
|---|---|---|
-all |
fail | Unlisted servers are explicitly not authorised |
~all |
softfail | Probably not authorised; be suspicious, do not reject on this alone |
?all |
neutral | The domain takes no position; of little use |
+all |
pass | Every server on the internet is authorised; a serious mistake |
The standard describes softfail as somewhere between fail and neutral, and says receivers should not reject mail on softfail alone. cPanel’s Email Deliverability tool recommends ~all by default and warns that its -all option makes every undefined host fail, so it should be enabled with care.
If you forget a service that sends as you, such as a booking tool, -all can get its mail rejected, and some receivers reject on an SPF fail before looking at DKIM, which hurts forwarded mail.
v=, v=spf1 not at the start, curly quotes pasted from a word processor, or include without its colon.all. Nothing after all is ever reached, because all matches everything.v=spf1 -all on them so nobody can use them for spoofing.Three quick checks cover most cases:
spf=pass.dig TXT example.com +short lists every TXT record so you can confirm there is only one SPF record.Every Start Bigger hosting plan comes with cPanel and its Email Deliverability tool, and our support covers email and DNS issues, so you can ask us to review your record. Outgoing mail is limited to 100 messages per hour per domain under our acceptable use policy, so send campaigns through a dedicated sending service and add its include to your existing record, not a new one. For the other record types, see DNS records explained simply.
v=spf1; a second record breaks the check entirely.include inside that one record, and remove the ones you stop using.include.~all, move to -all once every sender is listed, and never use +all.No. RFC 7208 forbids more than one SPF record on the same name, and two records produce a permerror, a permanent failure of the check. Merge them into one record by adding the newsletter tool's include to the record you already have.
Use ~all while you are still finding every service that sends as you, because it asks receivers to be suspicious rather than reject outright. Move to -all once the record lists every sender, ideally with DKIM and DMARC in place too. Never use +all, which authorises every server on the internet.
No. SPF checks the return-path address that readers never see, and it often breaks when mail is forwarded. Your domain also needs DKIM to sign messages and DMARC to tie the result to the visible From address.
No. An SPF record only applies to the exact name it is published on, so news.example.com needs its own record if mail is sent from it. That is also useful: moving campaign mail to a subdomain takes pressure off the main domain's lookup budget.
If your old SPF record listed the previous server's IP address directly, the new server is no longer authorised to send. Update the record to include the new server, remove what you no longer use, and send a test message.
A practical guide to creating email addresses on your company domain and setting up the DNS records that decide whether your messages reach the inbox.
An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.
A checklist for recording every online asset your business depends on, who controls it and when it renews, so a departing developer or employee never takes your domain or site with them.
We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)