SPF record
No senders yetPick the services that send your mail. A record with no senders lists no servers at all.
- Host
- yourdomain.com
- Type
- TXT
Pick the services that send mail as your domain. We build one v=spf1 record as you go, then count its DNS lookups against the limit of 10 before you publish.
Pick the services that send your mail. A record with no senders lists no servers at all.
Every term in the record above, in order, with what it lets through and what it costs.
yourdomain.comv=spf1SPF, version 1Comes first, so receivers know the record is SPF.~allCatch-all: soft failMail from a server not listed here gets a soft fail. Receivers decide what to do with it.Freeyourdomain.com itself, often written @. If it has an SPF record already, replace it: a domain may have only one.The record is built in your browser. Counting the lookups is the one step that reads public DNS.
yourdomain.comA TXT record that starts v=spf1 at the domain itself. Two or more of them is an error: receivers return permerror and treat the record as broken.
include:_spf.example.comEach include costs one lookup, plus every lookup inside its own record. We read each one from DNS and add them up, so you see the count before you publish.
bounces.example.comSome services send with a return-path on their own domain, so SPF is checked there, not on yours. They add nothing to this record, and the page says so.
What the count means, and what to do with the record.
One TXT record at your domain itself, starting v=spf1. A domain may publish only one, so if you have one already, merge the two. Merging multiple SPF records into one
Every include, a and mx in this record costs one, and so does every lookup inside each include. ip4, ip6 and all cost nothing. Counting your SPF lookups
The builder still makes the record, and says it is over. Receivers return permerror for it and SPF fails for every message. Drop a sender you no longer use, or move one to a subdomain with its own record. SPF PermError: too many DNS lookups
Some services send with their own return-path, so SPF is checked against their domain, not yours. An include on your record would spend a lookup and change nothing. Their mail lines up with your domain through DKIM.
~all or -all?-all asks receivers to fail mail from any server you did not list. ~all asks for a soft fail and leaves the decision to them. Start at ~all and move once every sender is in the record. Softfail, hardfail, and which to use
Fifteen an hour from one network. Building the record has no limit: only the count reads DNS.
The reading behind each finding, and the checks this page leaves to a sibling tool.
A new tool starts sending as you, or a vendor changes its record. Monitoring reads your DMARC reports and names each source they show.