Glossary · Authentication
What is an SPF permerror?
The short answer
An SPF permerror is a permanent error that means a mail server tried to read your SPF record and could not make sense of it. The usual causes are too many DNS lookups, two SPF records on one domain, or a typo. While the permerror lasts, SPF fails for every email you send.
Also called: SPF permanent error, permerror, SPF PermError, spf=permerror
By Ali Tahir Sajjad · Updated · 3 min read
SPF permerror: what to remember
- Permerror is short for permanent error: your SPF record itself is broken, and it stays broken until you fix it.
- The top causes are more than 10 DNS lookups, two SPF records on the same domain, and typing mistakes.
- An SPF permerror counts as a failed SPF check, so more of your email goes to spam.
- It is always fixed in your DNS, by correcting the one SPF record.
What does SPF permerror mean?
Permerror is short for permanent error. An SPF permerror means a mail server tried to check your SPF record and could not, because something is wrong with the record itself.
SPF is the record in your DNS that lists who may send email for your domain. Normally a receiving mail server reads it and answers “pass” or “fail”. With a permerror, it cannot get that far. The record is unreadable.
Think of giving a delivery driver an address written on a torn piece of paper. He is not saying the address is wrong. He is saying he cannot read it. Asking him again tomorrow will not help. You have to write it out again properly. That is why the error is called permanent.
What causes an SPF permerror?
There are four common causes.
- Too many DNS lookups. SPF allows only 10. Each
includecosts at least one, and includes can hide more includes inside them. This is the most common cause on busy domains, and it is the problem SPF flattening is meant to solve. - Two SPF records on one domain. A domain must have exactly one record that starts with
v=spf1. People often add a second one when they sign up for a new tool, instead of adding to the first. - A mistake in the record. A missing space, a misspelled word such as
inlcude, or a stray character. - An include that leads nowhere. The record points to a domain that has no SPF record, often because a service was shut down or the name was typed wrongly.
An SPF permerror example
Here is a domain with two SPF records, which is not allowed:
example.com TXT v=spf1 include:_spf.google.com ~all
example.com TXT v=spf1 include:servers.newsletter.example ~all
A mail server that receives email from this domain cannot tell which record to use, so it gives up. You can see the result in the email header:
Authentication-Results: mx.example.org;
spf=permerror (multiple SPF records found)
The fix is to combine both into one record:
example.com TXT v=spf1 include:_spf.google.com include:servers.newsletter.example ~all
SPF permerror vs temperror vs fail
| Result | What it means | Who fixes it |
|---|---|---|
| permerror | Your SPF record is broken and cannot be read | You, in your DNS |
| temperror | A temporary DNS problem stopped the check | Nobody. It usually clears by itself |
| fail | The record is fine, but this server is not on your list | You, by adding the server, if it is really yours |
| pass | The record is fine and the server is on your list | Nothing to fix |
How to fix an SPF permerror
- Find the cause. Paste your domain into an SPF checker such as MXToolbox. It tells you whether you have two records, too many lookups or a typo.
- If you have two records, merge them into one and delete the other.
- If you have too many lookups, remove the includes for services you no longer use.
- If there is a typo, correct it. The record must start with
v=spf1and end with~allor-all. - Save, wait a few minutes and test again until the result is
spf=pass.
If you would like to see what a correct record looks like, our guide to setting up SPF, DKIM and DMARC shows how the SPF record is written.
SPF permerror and cold email
An SPF permerror is quiet. Nothing bounces and no alarm goes off. Your emails still leave. They just start landing in spam more often, and you may not notice for weeks.
It also weakens the next check in line. DMARC needs SPF or DKIM to pass. With an SPF permerror, everything depends on DKIM alone, and if that has a problem too, DMARC fails.
The good news is that a domain used only for cold email should never get near a permerror. It needs a single SPF record with a single include, for Google or for Microsoft, so there is very little that can go wrong.
When PureMail sets up your Google Workspace inboxes or Microsoft 365 inboxes, our team writes that one SPF record on every domain and checks that it passes.