SPF records

If emails you send from your domain through our server are bouncing back, a missing or incorrect SPF record is usually the reason. An SPF (Sender Policy Framework) record lets the recipient’s email provider confirm your domain is allowed to send mail through us. This guide covers the record to add.

The record to add

Our sending server is a:smtpweb.uk.endis.com, and we make sure that entry always points at whichever of our servers is handling your mail. Add it to your domain’s DNS as a single TXT record, alongside anything else your domain manager recommends. If they don’t suggest anything in particular, this is usually enough:

v=spf1 mx a:smtpweb.uk.endis.com ~all

If your site is on our US server, use a:smtpweb.us.endis.com in place of the UK entry throughout.

If you also send email through another provider, include theirs in the same record. For Google Workspace:

v=spf1 a:smtpweb.uk.endis.com include:_spf.google.com ~all

For Microsoft Outlook or 365:

v=spf1 a:smtpweb.uk.endis.com include:spf.protection.outlook.com ~all

Checking your record

If you need a more tailored record, the SPF Wizard will build one for you. Once it’s in place, you can confirm it’s valid with the Kitterman SPF validator.

---

Good to know

• You should only ever have one SPF record. More than one makes them all invalid.
• You can only set up SPF where you control the domain’s DNS, so you can’t verify a Gmail or Hotmail address this way. If you’re sending from a non-domain address, set it as the ‘reply to’ and use noreply@hubb.church as the ‘sent from’ address, so your mail delivers and replies still reach you.
• SPF is one of three email-authentication records. There’s more on DKIM and DMARC in our email authentication guide.