Wiki / Email

Warning: SPF recordno SPF record found

The domain does not publish which servers may send mail in its name, so a recipient's mail system cannot tell your server from a forger's. Since 1 February 2024 Gmail requires SPF or DKIM from every sender; the record takes 10 minutes.

What it does not mean. It does not mean your mail is already being rejected: if your messages are DKIM-signed, Gmail's requirement is met. SPF checks the technical sender address (MAIL FROM), not the one the reader sees, so on its own it does not stop forgery: that takes DMARC. We check only the domain itself; every subdomain needs its own record.

Aleksandr IzmalkovFacts checked:

In our report
Warning (yellow), category weight 0.8 of 2.0. A record with +all: risk (red)
Time to fix
10 minutes if you know every system that sends in your name
Can it break things
Yes: with -all, mail from a sender you forgot fails the check

How to fix it

SPF is a single TXT record on the domain itself (name @): v=spf1, the list of senders, and a closing all. We evaluated every line below on 18 November 2026 with the SPF checker pyspf 2.0.14.

Your own mail server

@   TXT   "v=spf1 ip4:198.51.100.7 -all"

Replace 198.51.100.7 with your server's public IP address. ip4 and ip6 cost no DNS lookups.

Google Workspace

@   TXT   "v=spf1 include:_spf.google.com ~all"

The value from Google's documentation; Google recommends ~all. google.com publishes this same record.

Microsoft 365

@   TXT   "v=spf1 include:spf.protection.outlook.com -all"

The value from Microsoft's documentation; Microsoft recommends -all together with DKIM and DMARC.

Several senders: still one record

@   TXT   "v=spf1 ip4:198.51.100.7 include:_spf.google.com -all"

Take the include: value of a newsletter or invoicing service from its documentation and add it to the same record.

A domain that sends no mail

@   TXT   "v=spf1 -all"

Recommended by RFC 7208, section 10.1.2. This is what example.com publishes.

How to check

dig +short TXT example.com | grep spf1

Expected

"v=spf1 -all"

Exactly one line must come back. None: there is no record. Two: permerror.

Terminal: dig shows the SPF records of aguard.lt, google.com and example.com ending in ~all and -all
Real records on 18 November 2026: an own server listed by IP (aguard.lt), an include: (google.com) and a domain that sends no mail (example.com). Our server's IP address is replaced with an example one.

What can break

  • Two v=spf1 records on the same domain produce permerror, and SPF stops working altogether. It usually happens when a second record is created for a new service instead of extending the first.
  • More than 10 DNS lookups (include, a, mx, exists, redirect; nested include terms count too) produce permerror. In our test 10 include terms still evaluated and 11 returned “Too many DNS lookups”. _spf.google.com and spf.protection.outlook.com cost one lookup each today.
  • With -all, mail fails from any system you left out: website forms on another server, a newsletter tool, invoicing software.

Possible values

The ending says what to do with servers that are not on the list. Rules from RFC 7208 (2014, current).

RecordResult for an unlisted serverWhen to choose
-allfail: the server is not authorisedWhen the list of senders is complete
~allsoftfail: receivers should not reject on this aloneWhile you are still finding all senders; fine together with DMARC
?allneutral: treated exactly like a domain with no recordNever; a warning in our report
no allSame as ?allOnly when the record ends with redirect=: such a record is valid
+allpass: the whole internet is allowedNever; a risk in our report
ptrA mechanism that checks reverse DNSObsolete: RFC 7208 (2014) says not to publish it
DNS type SPFA separate record type (99)Removed by RFC 7208 (2014): publish TXT only

Our data

13.4%

of 64,910 inspected .lt domains (8,685) have no SPF record. 86.6% (56,225) have one. Dataset, 16 November 2026

Sources

Next