An SPF (Sender Policy Framework) record is a TXT record in your domain’s DNS. It identifies the mail servers authorised to send using that domain. Receiving mail systems can check the sending server against this policy as part of their authentication and filtering process.

Correct authentication helps protect your sending identity and supports deliverability. It does not guarantee inbox placement: reputation, message content, recipient engagement and the receiving provider’s policies also matter. The Pulseem team can help you confirm the SPF configuration needed for your account.

What is SPF?

SPF lets a domain owner publish a sending policy in DNS. Technically, it checks the domain used in the SMTP envelope sender (MAIL FROM), or the HELO identity in applicable cases. This is not necessarily the same as the From address a reader sees in an email.

How does it work?

  1. Your email platform sends a message.
  2. The recipient’s mail server receives the connection.
  3. It looks up the SPF policy for the relevant sending domain.
  4. It evaluates the sending IP address against that policy.
  5. It uses the result alongside other checks to decide how to handle the message.

Understanding an SPF record

A record may look like this:

v=spf1 ip4:203.0.113.10 include:_spf.example.com ~all

This is an illustration only. Do not copy these example values into your domain’s configuration.

  • v=spf1 identifies the SPF version.
  • ip4: and ip6: specify authorised IP addresses or ranges.
  • a and mx authorise addresses derived from the relevant domain’s address or mail-exchanger records.
  • include: checks another domain’s SPF policy, commonly the policy supplied by an email service.
  • ~all returns softfail for sources not matched earlier.
  • -all returns fail for sources not matched earlier. Use it only after accounting for all legitimate senders.

The receiving system decides how to handle a fail or softfail result; neither is a universal instruction guaranteeing delivery or rejection.

How to configure SPF

  1. List every legitimate sending source: your business email, email marketing platform, CRM, website forms and other services.
  2. Obtain the exact configuration from each provider. For Pulseem, ask our team for the values appropriate to your account.
  3. Open the DNS management panel at the provider hosting your domain’s DNS zone.
  4. Create or update the TXT record for the sending domain specified by your provider. Merge authorised sources into its existing SPF policy instead of adding a second SPF record.
  5. Allow DNS caches to refresh. Changes may appear within minutes or hours, but some providers advise allowing up to 48 hours.
  6. Validate the record and send test messages from every sending system.

Common mistakes

  • Multiple SPF records: publish one SPF policy per domain name. Separate SPF records cause an evaluation error.
  • Too many DNS lookups: SPF limits evaluation to 10 DNS-lookup-causing terms, including nested checks. Review complex include chains.
  • Missing senders: review your policy whenever you add or replace a sending service.
  • Switching to fail too early: an incomplete policy ending in -all can cause legitimate messages to fail SPF.

SPF is part of email authentication

Use SPF together with DKIM and DMARC. SPF alone does not verify the message body or directly authenticate the visible From header. Review your complete sending setup and test it before launching campaigns.

Frequently asked questions

Where do I configure SPF?

In the DNS zone for the relevant sending domain, as a TXT record. Your email provider supplies the required values; the DNS provider hosts the record.

Can I use two SPF records?

No. Combine the legitimate sending sources into one policy for each domain name.

When will a change take effect?

It depends on DNS caching and TTL settings. Allow the time recommended by your DNS provider and verify the published result.

What if I have no SPF record?

Messages may still be sent, but the receiver cannot confirm authorisation through SPF. Delivery depends on its policies and other authentication signals.

Need help with your sending setup? Contact Pulseem.