Boost Your Sales with WhatsApp Marketing
Drive more sales and promote your products and services directly to customers through the world's most popular messaging app.
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.
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.
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.
-all can cause legitimate messages to fail SPF.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.
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.
No. Combine the legitimate sending sources into one policy for each domain name.
It depends on DNS caching and TTL settings. Allow the time recommended by your DNS provider and verify the published result.
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.