| include |
Yes, and every counting term inside the record it points to |
It triggers a recursive evaluation of the other domain’s record (section 5.2). Only the result is used: a -all inside it does not end your check. If the target publishes no SPF record, the include is a permanent error. |
| a |
Yes, one |
An address lookup of the name, and it matches AAAA records too (section 5.3). With no name, it means the domain the record is published on. |
| mx |
Yes, one |
An MX lookup, then an address lookup on each mail server it returns (section 5.4). One mx term must not lead to more than 10 address lookups, or it is a permanent error. The same section says “the number of MX resource records queried is included in the overall limit of 10”; this counter counts each mx term once and shows how many mail servers it found, so treat a total of 8 or 9 with a multi-server mx as a minimum. |
| ptr |
Yes, one |
RFC 7208 says this mechanism SHOULD NOT be published (section 5.5). It looks up the reverse DNS of the sending address. |
| exists |
Yes, one |
An A lookup of the name you build, usually with macros, so it can depend on the sender’s address (section 5.7). |
| redirect= |
Yes, one, and the terms in the record it points to |
Hands the check to another domain’s record once every term has failed to match (section 6.1). It must be ignored when the record has an all term, wherever the two are written. |
| ip4, ip6, all |
No |
Section 4.6.4 lists them as the terms that cause no DNS query, so addresses are free however many you list. |
| exp= |
No |
It only causes a lookup “at a later time”, when a message is being rejected (section 4.6.4). |