SPF record with DNS lookup count

Domain administrators can build an SPF entry when they need to compose the record while keeping track of its DNS lookup count.

Draft an SPF record and count its DNS lookups at the same time, giving administrators a clear record to review before it is used.

How to use

Type the domain you are working on, then add one mechanism per line, such as an include or an IP range.
Load a text file if your mechanism list already exists, otherwise paste it straight into the input area.
Run the generation to assemble the record and see how many DNS lookups it triggers.
Review the output, drop unnecessary mechanisms when the lookup count climbs too high, then generate once more.
Copy the final record into your DNS zone once you have checked every entry.

Example

The sample describes a domain with an include, an IPv4 range and a closing policy keyword. After generating, study the shape of the resulting record and the lookup count reported, which grows with the number of lookup-consuming mechanisms you added.

Limits and formats

The builder only assembles and counts; it publishes nothing, so you still have to paste the value into your DNS zone yourself.
The lookup counter follows mechanisms that trigger DNS queries and says nothing about whether receivers will accept your policy.
A long list of includes can approach limits that some mail services enforce on published records.
Check the spelling of each mechanism, because a typo may still pass through the generation step unnoticed.

Where processing happens

The whole process runs inside your browser, so the domain and the mechanisms you enter never leave your device and are not transmitted anywhere. That means you can draft a record without an account and without disclosing anything about the way your domain sends mail.

Frequently asked questions

Can I build records for several domains at once?

No, one generation handles one domain and its own list of mechanisms. Repeat the operation for each domain and keep the outputs apart so you do not mix two sending policies inside a single record.

What happens if I list the same mechanism twice?

It appears twice in the resulting record and may be counted twice in the lookup total. Read through your list before generating and remove duplicates to keep the record clean.

Does the lookup count replace a live test of my zone?

No. The counter helps you anticipate how many DNS queries your mechanisms imply, but only a check against the published zone shows how receivers actually see your policy.