Glossary

SPF

Sender Policy Framework

Definition

Sender Policy Framework (SPF) lets a domain specify which servers may send email using its delivery-level sender identity.

Receiving servers compare the sender's server with rules published in DNS. A pass does not establish that the message is safe or the visible sender is genuine.

A customer may include “SPF” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

Sender Policy Framework (SPF) is an email-authentication mechanism that lets a domain publish which servers are allowed to send mail using its delivery-level identity. A receiving mail server checks the connecting server against those rules.

The identity checked is normally the envelope sender used during delivery, called MAIL FROM, and SPF can also check the server's HELO identity. These are not necessarily the From address displayed in an inbox. An SPF pass therefore does not, by itself, prove that the visible sender is genuine.

Hypothetical example: a small firm uses one provider for staff email and another for invoices. Its administrator needs to account for both legitimate sending services. If the invoice service is omitted, authentic invoices may fail SPF; if unnecessary senders are allowed, the policy becomes less useful.

Inventory all services authorised to send mail from your domain and update the SPF record when those services change. Keep the record within SPF's DNS lookup limits and avoid authorising sources that do not send on your behalf. Forwarding can complicate SPF because the receiving server may see a different sending server. SPF works alongside DKIM and DMARC; none of these mechanisms establishes that an authenticated message contains an honest request or encrypts email.

Sources: IETF RFC 7208: Sender Policy Framework.