IPTOOL TR My IP

Email

SPF Generator: build a TXT record

Build an SPF TXT from ip4, ip6, include and -all.

Build a one-line SPF TXT from ip4, ip6 and include. You publish it in DNS; watch the 10-lookup rule.

Queries leave from this Linux server, not your ISP DNS. Free. Cached answers can differ for a short time.

Today 0 / 40 queries

SPF Generator fields

Empty fields are skipped. Multiple values can be comma- or line-separated.

Field Adds Example
IPv4 ip4: mechanism 203.0.113.10 or /24
IPv6 ip6: mechanism 2001:db8::1
Include Another SPF chain (1 lookup) _spf.google.com
Policy all suffix -all production · ~all transition

What SPF Generator does

Produces TXT: v=spf1 + your ip4/ip6/include + chosen all. SPF Checker only looks up an existing record; this page is generator-only.

Paste into the apex TXT. Do not publish two v=spf1 records. Generation runs here; IPTOOL does not write your DNS panel.

Examples

Workspace
include:_spf.google.com → -allEnough if that is your only SMTP.
Own server
ip4:203.0.113.10 -allHosting egress IP.
Mixed
ip4:… include:_spf.google.com -allCount lookups.

Before you publish

Validate with SPF Checker. If over 255 characters, split TXT or consider flattening (Pro). We never recommend +all.

Super box prefix spfgen: also lands here. Flattening is a separate Pro tool; this page only builds a new record.

Frequently asked questions

How is this different from Checker?

Checker reads the existing SPF record; creation lives on this Generator page.

Does it write DNS?

No. You paste the line into your panel.

Which policy?

Use ~all while transitioning, then -all. We do not recommend +all.

Record too long?

Stay under 255 characters or split with includes. Pro SPF Flattening collapses chains.

Prefix?

Type spfgen: in the super box.

Multiple includes?

Yes; each include counts as one lookup. Stay at or below 10.

Can ip4 use CIDR?

Yes, e.g. ip4:203.0.113.0/24. Avoid overly wide ranges.