Surftec customers will be recognised automatically when they use these tools from their office network.
Customer sign-in is coming soon.
SPF checker and builder
Check which servers may send email for a domain, see how much of each SPF limit is used, and build and test a new record before you publish it.
The limits SPF sets
Limit
Used now
Allowed
Status
Where it is set
SPF records at the domain Two or more is a permanent error; none means no SPF.
–
1
Note
RFC 7208 §3.2, §4.5
DNS lookups Every include, a, mx, ptr, exists and redirect, counted through every nested record. ip4, ip6 and all cost nothing.
–
10
Note
RFC 7208 §4.6.4
Void lookups Lookups that find no record or a name that does not exist. More than 2 is a permanent error.
–
2
Note
RFC 7208 §4.6.4
Mail servers behind one mx term Each mx term may resolve to at most 10 mail server names.
–
10
Note
RFC 7208 §4.6.4
Names examined for one ptr term ptr is slow and unreliable; the RFC says not to use it.
–
10
Note
RFC 7208 §4.6.4, §5.5
Record length (characters) A recommendation, so the reply fits one DNS packet.
–
450
Note
RFC 7208 §3.4
Characters in one TXT string Fits in one string.
–
255
Note
RFC 7208 §3.3, RFC 1035
Whole TXT answer for the domain (bytes, estimated) Every TXT record at the domain is sent together. Over 512 the reply needs EDNS or TCP, which some networks block.
–
512
Note
RFC 7208 §3.4
Nesting depth No depth limit of its own: nested records are bounded by the 10 lookups.
–
No fixed limit
Note
RFC 7208 §4.6.4
Used now is counted from live DNS at the time of this check. A record over a limit is treated as broken by receiving mail systems, not as partly working.
Test with a real emailNothing is uploaded
Send an email from the domain to a mailbox you can open elsewhere (Gmail or Outlook.com work well), view the message source or headers there, and paste them here. The headers are read in your browser and are not sent to Surftec.
About this tool
SPF (Sender Policy Framework, RFC 7208) is one TXT record at your domain listing the servers allowed to send its email. Receiving mail systems read it to spot forged mail. A record that breaks one of the limits in the standard is not partly right: receivers treat it as a permanent error and SPF fails for every message, genuine ones included.
The limits are: one SPF record for a domain; at most 10 DNS lookups, counting every include, a, mx, ptr, exists and redirect through every record those pull in; at most 2 lookups that find nothing; at most 10 mail servers behind one mx term; 255 characters in one TXT string; and a record short enough (450 characters is the recommendation) for the whole TXT answer to fit a 512 byte DNS reply. The checker counts each of these from live DNS and shows the figure beside the limit.
The builder starts from the record that is published now. Tick the services that send your email, add your own servers' addresses, and select Test this record: the draft is checked against live DNS exactly as a published record would be, so you see the real lookup count before anything changes. When it passes, the page shows the DNS entry to add.
Common questions
Why does SPF fail with "too many DNS lookups"?
An SPF check may make at most 10 DNS lookups, counting every include inside every include. Microsoft 365 alone uses 2 or 3. Remove services you no longer send through, or replace an include with the addresses it lists when those are few and fixed. The tree on the result page shows what each include costs.
Can a domain have two SPF records?
No. Two TXT records starting v=spf1 make SPF fail for every message. The checker merges them into one record for you to publish in their place.
Should SPF end in ~all or -all?
Use ~all (soft fail) while you are still finding every sender, and -all once DMARC reports show them all passing. DMARC decides what finally happens to failing mail, so ~all with DMARC at reject is as strong as -all.
Does ip4 count towards the 10 lookups?
No. ip4, ip6 and all need no DNS lookup. Only include, a, mx, ptr, exists and redirect count.
What is a void lookup?
A lookup that finds no record, or a name that does not exist. More than 2 in one SPF check is a permanent error, so an include pointing at a service that has closed can break the whole record.
Does this tool change my DNS?
No. It reads public DNS and shows what to publish. You add the record at the company that hosts your DNS.