From a list of senders to one record
Write down who sends as you
Before touching the form, list every system that puts your domain in the From address: the mailbox provider, a newsletter platform, an invoicing app, a booking system, any outreach tool. Each one needs to be in the record.
Tick mx or a only if they really send
mxauthorises the servers that receive your mail andaauthorises the server your website runs on. With a hosted mailbox such as Microsoft 365 or Google Workspace, neither usually sends, so leave them off and use the provider's include instead.Paste each provider's include
Copy the include value from each vendor's own setup page into the include box, one per line. You can paste it with or without the
include:prefix; the builder normalises it.Add fixed addresses
If an office server or a device such as a scanner relays mail from a known address, enter it in the IPv4 or IPv6 box. Ranges in CIDR form, such as
198.51.100.0/28, are accepted.Choose the ending and copy
Pick
~allwhile you confirm the list is complete,-allonce you are sure. Copy the value for your DNS panel, or the zone file line if you edit a zone file directly.
Example: Microsoft 365 plus a newsletter tool and an office relay
Hollins Letting, a fictional estate agency, sends day-to-day mail through Microsoft 365, a monthly newsletter through a mailing service and property alerts from one office server at a fixed address. The mx and a boxes stay unticked because neither the mail exchangers nor the web host sends anything.
The builder reports that the record uses 2 of the 10 DNS lookups on its own. That figure does not include lookups hidden inside each provider's include, so check the finished domain with the SPF checker once it is live.
Your domain: hollinsletting.example
IPv4: 198.51.100.24
Includes: spf.protection.outlook.com
_spf.mailer.example
Mail from anywhere else: ~allType: TXT Host / name: hollinsletting.example (or @) Value: v=spf1 ip4:198.51.100.24 include:spf.protection.outlook.com include:_spf.mailer.example ~all Note: This record itself uses 2 of the 10 DNS lookups.
What the builder warns about
| Situation | What you see | Why it matters |
|---|---|---|
| Address with a value over 255 or a leading zero | Error | Receivers cannot parse the term, which can break SPF entirely |
| IPv4 range wider than a /16 | Warning | You may be authorising thousands of servers you do not control |
| Nothing listed except all | Warning | Fine for a parked domain that never sends, wrong for one that does |
| ?all chosen | Warning | Neutral gives receivers no instruction at all |
| More than 10 lookups in the record itself | Error | Receivers return a permanent error and SPF fails |
| Value over 255 characters | Note | DNS stores it as several strings; the zone line is already split |
| Value over about 450 characters | Warning | Large answers can exceed 512 bytes; prune unused senders |
Questions people ask
What should an SPF record look like for Google Workspace?
For a domain that only sends through Google Workspace, the common form is v=spf1 include:_spf.google.com ~all. Type that include into the builder with mx and a unticked. If you also send through other tools, add their includes on separate lines so the result stays a single record covering every sender.
Should I use ~all or -all?
Use ~all (soft fail) while you are still discovering which systems send as your domain, because a forgotten sender will be marked suspicious rather than rejected outright. Move to -all when your DMARC reports show nothing legitimate failing. The builder also offers ?all, but neutral gives receivers no guidance and is rarely the right choice.
Does a separate cold email domain need its own SPF record?
Yes. SPF is published per domain, so an outreach domain such as getbrightwell.example needs its own record listing only the service that sends from it. Keeping outreach on its own domain also means your main domain's record stays short and its reputation is not tied to campaign results.
Why does the lookup count look lower than another checker shows?
This builder counts only the terms in the record you are writing: each include, a, mx and similar term costs one. It cannot see inside a provider's include without querying DNS, and many includes contain further includes. A checker that follows the whole chain will often show a higher total, which is the figure receivers actually apply.
How long does a new SPF record take to work?
As soon as your DNS host publishes it, new lookups see it. Resolvers that cached the old answer keep it until its TTL runs out, often between a few minutes and a few hours. A DNS propagation checker shows which public resolvers already return the new value.
Where your data goes
Everything happens on this page: the domain, addresses and includes you type are turned into a record locally. Nothing is looked up and nothing is sent to Map Extract or a third party.
Checked against the tool on