SPF as published in public DNS.
v=spf1 include:_spf.mailertogo.net include:_spf.google.com ~all
It parses cleanly, every name it includes publishes SPF, and it fits inside the ten-lookup budget.
include:
plus everything inside it.
| Term | What it does | Lookups | Running total |
|---|---|---|---|
include:_spf.mailertogo.net
|
Applies _spf.mailertogo.net's own SPF record here — every sender that record authorises, this one authorises too. | 1 | 1 |
include:_spf.google.com
|
Applies _spf.google.com's own SPF record here — every sender that record authorises, this one authorises too. | 1 | 2 |
~all
|
Everything not matched above is a softfail: receivers accept the mail but mark it as unauthorised. This is the usual, safe choice. | — | 2 |
An
include:
costs one lookup for itself plus every lookup inside the record it pulls in, which is why a record
with four includes can be nowhere near four.
ip4:
and
ip6:
are free — they are already addresses.
SPF includes _spf.mailertogo.net This record is correct as published — there is nothing here to change.
SPF is defined by RFC 7208. We read the same public DNS a receiving mail server reads, and cache each answer for a few minutes. Nothing about this lookup is stored.