Site AI Auditpor Internet Solutions

SPF Findings Explained: Missing, Multiple, +all and Neutral

16 de novembro de 20267 min de leituraEntregabilidade de e-mail
SPF Findings Explained: Missing, Multiple, +all and Neutral

Short answer: SPF is a DNS record that lists the servers allowed to send e-mail for your domain. Site AI Audit checks it for five problems: no SPF record, more than one SPF record and SPF that allows any server (+all), all of which are critical; SPF with a neutral or missing “all” rule, which is a warning; and an SPF record that needs more than 10 DNS lookups, which is critical. Each can make your real mail land in spam or let others send as you.

What SPF is, in one minute

SPF stands for Sender Policy Framework. You publish a single TXT record in your DNS that starts with v=spf1 and lists who may send mail from your domain: your mail provider, your newsletter service, your website server. When a receiving server gets a message that claims to come from you, it looks up this record and checks whether the sending server is on the list. If it is, the check passes. If it is not, the receiver can treat the message with suspicion.

SPF is one of three records that work together, with DKIM and DMARC. It is also the one that is easiest to get wrong, because the rules are strict and small mistakes switch the whole record off. The e-mail area of the audit report starts with SPF for that reason, and its findings are mostly critical.

Finding 1: No SPF record (critical)

The report says there is no SPF record, and explains that without SPF anyone can send e-mail pretending to be you, and your real e-mails are more likely to land in spam. The advice is to publish a TXT record such as “v=spf1 include:” followed by your mail provider’s SPF name, then “-all”. Each mail provider documents the include value. For common setups, the article with SPF record examples shows complete records.

Before you publish, make a list of everything that sends mail for your domain. Missing one service means its mail will fail the check, so include every sender: the mailbox provider, the web shop, the invoicing tool and any CRM or helpdesk.

Finding 2: More than one SPF record (critical)

A domain may have only one SPF record. If there are two, SPF fails entirely, and receivers usually treat that as a permanent error. The explanation in the report says that multiple records make SPF fail, which hurts deliverability, and the advice is to merge them into a single v=spf1 record.

This typically happens when you add a new service and its instructions say “add this TXT record”, so you add a second line instead of editing the first. The right action is to combine the include parts into one record. The article on merging two SPF records shows how, step by step.

Finding 3: SPF allows any server (+all) (critical)

The ending of an SPF record says what to do with senders that are not on the list. “-all” means reject them, “~all” means treat them as suspicious and “+all” means accept everyone. A record ending in +all makes SPF pointless, because it says that any server in the world may send as you. The report calls it useless and an invitation to spoofing, and the advice is to replace +all with ~all or -all.

Few people write +all on purpose. It appears when someone is frustrated that mail is failing and “opens up” the record to make the problem go away. If you see this finding, the right answer is to fix the underlying cause: list the real senders and then end the record with ~all or -all.

Finding 4: SPF does not say what to do with other senders (warning)

This warning appears when the record ends with “?all”, which is neutral, or has no “all” mechanism at all. A neutral rule gives receivers no instruction against spoofed mail. The advice is to end the record with ~all (soft) or -all (strict). Many businesses use ~all first and move to -all when they are confident that every sender is listed. With DMARC in place, either is fine; the strictness choice matters less once DMARC does the enforcement.

Finding 5: SPF needs more than 10 DNS lookups (critical)

SPF has a hard limit: when the receiver evaluates the record, it may perform no more than 10 DNS lookups, counting includes and some other mechanisms. Over the limit, SPF fails and legitimate mail may be rejected. The report shows the number, for example “SPF needs 14 DNS lookups (limit is 10)”. This is the most technical of the five, and it appears in companies that use many services, because each include can bring its own nested includes.

The advice is to remove unused include entries or to flatten the record. In practice:

If your record is also long in characters, remember that a single DNS string holds 255 characters; the article on TXT records over 255 characters covers splitting.

The order in which to fix them

  1. Make sure there is exactly one SPF record. Missing or multiple records break everything else.
  2. List all senders. Cover every service before you tighten anything.
  3. Keep the lookups under 10. Count them with a lookup tool after each change.
  4. End the record sensibly. Use ~all or -all, never +all.
  5. Add DMARC and DKIM. SPF alone cannot protect forwarded mail; see how to fix a missing DMARC record.

Common mistakes

A few errors come up again and again. People add the include for their website host but forget the one for their mailbox provider. They copy a record from another domain, which lists the wrong servers. They paste a record with quotation marks that the DNS panel then doubles. They change the record on the wrong domain, for example the website’s domain when the mail uses another one. And they forget that SPF applies to the envelope sender, so mail sent through a forwarding service may fail even when your record is right. A test message to an outside address, with the headers inspected, tells you more than any number of guesses.

When mail comes from several systems

Growing businesses collect senders: the main mailbox, the web shop, a customer service tool, a newsletter service, a booking system. Each wants its own include in the SPF record, and that is how a record grows to the limit. Keep a simple list of every service that sends mail from your domain, with the date added and the person responsible. When a service is cancelled, remove its include on the same day. A list that is kept up to date keeps the lookup count under control and makes audits and DMARC reports far easier to read.

How to count lookups yourself

The audit shows the number it counted, but you can verify it. Start with the main record and count each include, a, mx and redirect as one lookup. Then open every include and count the lookups inside it. Repeat for the nested ones. A free SPF checker does this automatically and shows the tree. If the count is close to the limit, trim before adding anything new, because a new include from one provider can bring several lookups at once.

A worked example

A marketing agency’s report shows two critical findings at once: more than one SPF record and 13 lookups. The agency had added a record for its mailbox provider years ago and a second one for a newsletter tool last spring. The IT contractor merges them into one record, removes two includes for tools the agency had stopped using, and the count falls to 8. He ends the record with ~all. After a re-check, both critical findings are gone, and the agency’s newsletters stop landing in spam, a problem that had puzzled everyone for months. The cause had been visible in the DNS all along, but nobody had looked.

To see how your own SPF record looks to the outside world, check your website with Site AI Audit. The check needs a free account; the plans unlock the full report.

Related reading

The bottom line

SPF problems are mostly critical because they break your mail or invite spoofing. Keep exactly one record, list every sender, stay under 10 lookups and end with ~all or -all. Then run the check again to confirm.

FAQ

Can I have two SPF records if they are for different services?

No. A domain may have only one. Combine the parts into a single record.

Should I use ~all or -all?

Either clears the finding. ~all is the softer choice, and -all the strict one. Many start with ~all and tighten later.

What counts as a DNS lookup in SPF?

Mechanisms such as include, a, mx and redirect each cause lookups, and includes can trigger further lookups of their own.

Does SPF alone protect my domain?

No. It works best together with DKIM and DMARC. SPF alone can break when mail is forwarded.

How quickly does a new SPF record take effect?

Usually within minutes to hours, depending on the DNS time to live. Test with a message from an outside address.

#Email Authentication#Email Deliverability#SPF
Audite seu próprio site.Seu site está protegido contra invasões?
Auditar meu site
Internet Solutions

Mais da nossa equipe

Feitas pela Internet Solutions. Experimente nossos outros produtos — cada um economiza seu tempo de um jeito diferente.

internet-solutions.net ↗