What is SPF?
Sender Policy Framework (SPF) is an email authentication protocol that lets domain owners specify which mail servers are allowed to send email from their domain. SPF authorises specific outbound mail server IPs to send on a domain's behalf, so receiving servers can confirm that a message actually came from a server you approved.
By default, TouchBasePro supplies an SPF record that authorises the domains and IP addresses our service sends email through. That record sits with our domain, not yours. Some mail servers with stricter configurations will treat that as a red flag and cause delivery problems.
Why do I need to add TouchBasePro's SPF?
Some mail servers are configured to reject emails that arrive from an external server but carry your domain in the "From" address. Others will run additional checks before accepting the message, which can delay delivery or block it entirely.
Adding our SPF record to your domain's DNS tells receiving servers that you have explicitly authorised TouchBasePro to send on your behalf. That removes the ambiguity and reduces the chance of your emails landing in spam or being rejected.
What to add
v=spf1 include:touchbasepro.email
Add this as a TXT record in your domain's DNS settings.
Consider DKIM and DMARC for added email security
While you are making changes to your DNS, it is worth adding DKIM and DMARC at the same time.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to your outgoing emails. Receiving servers use it to verify that a message genuinely came from you and was not altered in transit. This improves your chances of reaching the inbox when sending bulk email. To set up DKIM for your TouchBasePro account, email support@touchbasepro.com and the support team will send you the instructions.
DMARC addresses a different problem: email spoofing. Most organisations have security software to protect staff inside their own email environment, but far fewer pay attention to what happens outside it.
Spoofing is a serious issue. Cybercriminals can insert any sender address into a forged email, which means they can impersonate your business or your staff to phish or attack other companies. The reputational damage can be significant.
A DMARC record on your domain lets you monitor all email being sent on your behalf and enforce a policy against unauthorised senders. If you want a free analysis of what is currently being sent on your domain, contact our Head of Business Development at des@touchbasepro.com and one of our email experts will follow up.
For more detail on the DMARC process TouchBasePro follows, read the overview here.
Frequently asked questions
- What is an SPF record and why does it matter for email deliverability?
- An SPF record is a DNS entry that lists the mail servers authorised to send email from your domain. Receiving mail servers check it to confirm a message came from a legitimate source. Without it, emails sent through a third-party platform like TouchBasePro may be flagged as suspicious or blocked.
- What SPF record do I need to add for TouchBasePro?
- Add the following TXT record to your domain's DNS: v=spf1 include:touchbasepro.email. This tells receiving servers that TouchBasePro is authorised to send email on your domain's behalf.
- What is the difference between SPF, DKIM, and DMARC?
- SPF specifies which servers can send on your domain. DKIM adds a cryptographic signature to each message so recipients can verify it has not been tampered with. DMARC builds on both by letting you monitor all email sent on your domain and enforce a policy against unauthorised senders. All three work together to protect your sender reputation and reduce spoofing.
- How do I set up DKIM for my TouchBasePro account?
- Email support@touchbasepro.com and the support team will send you the setup instructions for your account.