IONOS mail fails SPF because the record is missing, duplicated or too long
spf=fail or spf=softfail for a message sent through IONOSShort answer
SPF for IONOS mail fails when the domain's DNS does not include the IONOS sender, when there are two SPF records, or when the record needs more than 10 DNS lookups. If DNS is outside IONOS, you must add the IONOS entry yourself. Keep one record and allow time for DNS to spread.
Fix it fast
1Find out which cause you have
Read the SPF record that DNS really serves for the domain. There must be exactly one line starting with v=spf1.
dig +short TXT example.com2Match what you see, then jump to its fix
- 1
The domain's name servers are not IONOS, and the SPF record has no IONOS include.The DNS zone is at another provider and has no IONOS entryFix - 2
dig returns two TXT lines beginning v=spf1.Two SPF records exist for the domainFix - 3
permerror although only one record exists, and it includes many services.The record needs more than 10 DNS lookupsFix - 4
The record is right in your panel, but dig from outside still shows the old one.The change has not spread yetFix
- 1
What does the error look like?
spf=fail or spf=softfail for a message sent through IONOSSPF permerror
Cause 1 of 4
The DNS zone is at another provider and has no IONOS entry
1Check
IONOS says that if you use IONOS email accounts but manage your DNS zone elsewhere, you must set up the SPF entry with your DNS provider.
dig +short NS example.com2Fix
At your DNS provider, create the TXT record with the value IONOS shows for external DNS in its help page or your control panel. The help page gives this one.
v=spf1 include:_spf-us.ionos.com ~all3Verify
dig shows the record, and a new test message shows spf=pass.
dig +short TXT example.comConfirmed by ionos.com
Cause 2 of 4
Two SPF records exist for the domain
1Check
If more than one SPF record is found, the result is permerror. RFC 7208 says a domain must not publish multiple records that would lead to more than one being selected.
dig +short TXT example.com | grep -c "v=spf1"2Fix
Merge them into one record that lists every sender, ending in a single all term, then delete the extra record.
v=spf1 include:_spf-us.ionos.com include:sender.example.net ~all3Verify
The count command prints 1.
dig +short TXT example.com | grep -c "v=spf1"Confirmed by rfc-editor.org
Cause 3 of 4
The record needs more than 10 DNS lookups
1Check
include, a, mx, ptr and exists, plus the redirect modifier, count toward a limit of 10 DNS lookups. ip4, ip6 and all do not count.
dig +short TXT example.com2Fix
Remove services you no longer use, and replace some includes with ip4 or ip6 entries your provider documents as stable.
v=spf1 include:_spf-us.ionos.com ip4:203.0.113.10 ~all3Verify
A fresh test message shows spf=pass instead of permerror.
dig +short TXT example.comConfirmed by rfc-editor.org
Cause 4 of 4
The change has not spread yet
1Check
IONOS says a change can take up to 48 hours to spread worldwide and take effect.
dig +short TXT example.com @8.8.8.82Fix
Wait, and test again. Do not keep changing the record meanwhile.
# no change needed; recheck after DNS has spread3Verify
dig against a public resolver shows the new record.
dig +short TXT example.com @8.8.8.8Confirmed by ionos.com
How do I stop it coming back?
- Edit the one existing SPF record instead of adding another.
- Keep a list of the services allowed to send as your domain.
- Add DKIM and DMARC after SPF works.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Related fixes
Gmail rejects your mail with 550 5.7.26: no authentication information
rejected with a 5.7.26 error
Gmail returns 5.7.26 when a message is not authenticated.
4 causes, each with a fixCodeIgniter email does not send and shows no error message
$email->printDebugger() prints an empty result
CodeIgniter signals a failed email only by send() returning false, with no exception.
4 causes, each with a fixDjango send_mail fails or hangs with an SSL error
smtplib.SMTPException raised from send_mail()
Django has two secure modes that must not be mixed: EMAIL_USE_TLS for explicit TLS (STARTTLS, usually port 587) and EMAIL_USE_SSL for implicit TLS (usually port 465).
4 causes, each with a fixDKIM shows 'bad version' or 'unknown key type' because the DNS key record is malformed
dkim=fail (unknown key type)
These results mean the receiver found your DKIM key record but could not use it.
4 causes, each with a fixSmtpException: Unable to read data from the transport connection (net_io_connectionclosed)
System.Net.Mail.SmtpException: Unable to read data from the transport connection: net_io_connectionclosed.
The server closed the connection while SmtpClient was waiting for a reply.
4 causes, each with a fixDovecot refuses to start: Can't load SSL certificate, no valid PEM certificate
doveconf: Error: ssl enabled, but ssl_cert not set
Dovecot reads the ssl_cert setting as the file's contents, not a path, so in 2.3 the value must start with a less-than sign.
3 causes, each with a fix