In simple terms:
It’s a permission list for email senders tied to your website domain.

Why SPF Matters

SPF helps with:

• Preventing email spoofing – stops scammers from pretending to send emails from your domain.

• Improving deliverability – emails are less likely to land in spam.

• Building sender trust – receiving servers can verify you’re legitimate.

How It Works

When you send an email:

1. The receiving email server checks your domain.

2. It looks up your SPF TXT record in DNS.

3. It compares the sending mail server’s IP address to the allowed list.

4. If it matches → Pass
   If it doesn’t → Fail or SoftFail

What an SPF Record Looks Like

Example:

v=spf1 ip4:192.168.0.1 include:_spf.visualvisitor.com -all

Breaking It Down

• v=spf1 → Version (always required)

• ip4:192.168.0.1 → Allows this specific IP to send mail

• include:_spf.VisualVisitor.com → Allows Visual Visitor mail servers 

• -all → Deny everything else
  

You will be using the "include" rule

This is not the exact SPF, please reach out to support for the SPF record you need.

Common Endings

• -all → Hard fail (strict, blocks others)

• ~all → Soft fail (allowed but suspicious)

• ?all → Neutral

• +all → Allow all (not recommended)

Where You Add It

You don’t add SPF in your email app.
You add it in your DNS settings where your domain is hosted (like GoDaddy, Cloudflare, Namecheap, etc.).

Best Practices

• Only one SPF record per domain (combine services if needed).

• Include all services that send email for you (Visual Visitor, Microsoft, marketing tools, CRM platforms).

• Avoid +all.
  

Need assistance updating your SPF Record?