For the emails you send from your domain to reach the inbox (instead of being rejected or marked as spam), your domain's DNS must publish a correct SPF record. This guide explains what SPF is, the exact value you need, and how to set it up step by step — whether your DNS is hosted with us or with an external provider.
What is an SPF record?
SPF (Sender Policy Framework) is a small text note (a TXT record) published in your domain's DNS. It tells the rest of the world which servers are allowed to send email on behalf of your domain. Every time you send a message, providers such as Gmail, Outlook or Yahoo look up that record and check whether the server that delivered the message is on your authorized list:
- If it is → the message passes the check and has a much better chance of landing in the inbox.
- If it is not (or the record is missing or broken) → the message may go to spam or be rejected outright.
The correct SPF record for BanaHosting
This is the exact record your domain needs:
| Type | TXT |
| Name / Host | your domain (shown as yourdomain.com. or @ depending on the panel) |
| TTL | 14400 (or the default value your panel offers) |
| Value | v=spf1 +a +mx include:spf.jetsmtp.net ~all |
What each part means:
v=spf1— identifies the record as SPF version 1. Every SPF record must start with this.+a— authorizes the IP address of your website (the A record of your domain).+mx— authorizes your mail servers (the MX records of your domain).include:spf.jetsmtp.net— authorizes our outgoing email delivery network. This part is essential: our servers deliver your messages through this network so they arrive with the best possible reputation.~all— tells receiving servers to treat mail from any other source with suspicion (soft fail). This is the recommended closing tag.
Step 1 — Check what your domain has right now
Open mxtoolbox.com/spf.aspx, type your domain and press SPF Record Lookup. Three possible outcomes:
- It shows exactly
v=spf1 +a +mx include:spf.jetsmtp.net ~all→ perfect, you are done. - It shows a different value (missing
include:spf.jetsmtp.net, or leftovers from a previous provider) → edit it following Step 2. - It shows no SPF record, or more than one → fix it following Step 2 and the warning below.
Step 2, option A — Your DNS is managed at BanaHosting (most common)
If your domain uses our nameservers, you manage DNS from cPanel:
- Log in to cPanel.
- Go to Domains → Zone Editor.
- Click Manage next to your domain.
- In the filter, select TXT to list only text records.
- Look for a record whose value starts with
v=spf1.- If it exists: click Edit and replace the value with
v=spf1 +a +mx include:spf.jetsmtp.net ~all, then Save. - If it does not exist: click Add Record, choose type TXT, set the name to your domain, paste the value above and Save.
- If it exists: click Edit and replace the value with
Note: on accounts created recently the record is usually already in place — Step 1 confirms it in seconds.
Step 2, option B — Your DNS is managed elsewhere (Cloudflare, your registrar, etc.)
If your domain points to external nameservers, the record must be created at that provider (changes made in cPanel will have no effect). In your DNS provider's panel, add or edit a TXT record for your root domain with the value:
v=spf1 +a +mx include:spf.jetsmtp.net ~all
In Cloudflare: DNS → Records → Add record → Type TXT → Name @ → Content (paste the value) → Save.
A domain must have exactly one TXT record starting with
v=spf1. If there are two or more, the standard treats SPF as invalid (PermError) and your deliverability gets worse, not better. If you find several, merge them into a single record: keep one record and combine the include: parts. Example — if you also send campaigns through a third-party service, do not add a second record; use one combined record such as:v=spf1 +a +mx include:spf.jetsmtp.net include:servers.thirdparty-example.com ~all
Step 3 — Verify the change
- Wait for DNS propagation: usually a few minutes, up to a few hours depending on the previous TTL.
- Run the check again at mxtoolbox.com/spf.aspx. It should report a single valid SPF record with our
include. - Optional: send a test message to a Gmail account, open it and use Show original — you should see
SPF: PASS.
Common mistakes to avoid
- Two or more SPF records — the most frequent problem. Merge them into one (see the warning above).
- Old values left behind from a previous hosting provider (their
include:orip4:entries). Remove what no longer applies. - Record created on the wrong name (for example on
www): it must be on the root domain. - Typos or added quotes: paste the value exactly as shown, with single spaces between parts.
- Editing cPanel when your DNS lives elsewhere: always change the record where your nameservers actually point (Step 1 tells you what the world sees).
Going further: DKIM and DMARC
SPF is the essential piece, and two more records complete the picture:
- DKIM (digital signature): if your DNS is with us, cPanel manages it automatically. You can confirm it in cPanel → Email → Email Deliverability — your domain should show as Valid. If your DNS is external, that same screen shows the DKIM record you need to copy to your provider.
- DMARC (policy): optional but recommended. A safe starting record is a TXT on
_dmarc.yourdomain.comwith the valuev=DMARC1; p=none; rua=mailto:postmaster@yourdomain.com
Need a hand?
If you prefer, open a support ticket and our team will review and configure your domain's records for you — just tell us the domain name.