Suped

SPF record generator

Use this free SPF record generator tool to build one TXT record or edit an existing one, then check nested DNS lookups before publishing.

Add include

Advanced

Or select from popular sending sources

Your SPF record

v=spf1
Total

Generate or edit SPF records without hand editing syntax

SPF record builder
Use this SPF record generator tool to build one TXT value or edit an existing record. Add provider includes, IP ranges and a policy, then check nested DNS lookup counts. After publishing, use the SPF checker to verify live DNS and lookup counts. For ongoing records that change as senders change, use Suped's hosted SPF for managed updates.
Get started
outcome left image

Merge multiple SPF records into one TXT record

Import the existing SPF value, retain authorized senders, and add the new provider or IP. Publish one replacement v=spf1 record—not a second record—then verify live DNS.

SPF record format: include multiple sending providers

SPF starts with v=spf1, lists authorized mechanisms and usually ends with one all mechanism. This Google Workspace/Microsoft 365 example applies only when both send for your MAIL FROM domain; follow each provider's current instructions.
v=spf1 include:_spf.google.com include:spf.protection.outlook.com ~all
Use only when both services send for your MAIL FROM domain; preserve other legitimate senders.

Check the SPF lookup limit before publishing

The generator counts live nested DNS lookups; recheck when provider DNS or senders change. Exceeding ten lookups causes SPF PermError, not certain rejection, and DMARC can still pass through aligned DKIM.

SPF generation that avoids common mistakes

Use the SPF record generator to create one clean TXT record, preserve existing senders, add new email platforms, and copy the exact DNS value to publish. It keeps SPF syntax readable so teams do not accidentally create duplicate records or weak all mechanisms.
SPF record
example.com
TXTv=spf1 include:_spf.google.com ~all
Clean TXT output
Copy one SPF value with includes, IP addresses, optional a or mx, and a clear all mechanism.
include:_spf.google.com
ip4:192.0.2.24
mx
Provider and sender additions
Choose supported provider presets, including Google Workspace and Microsoft 365, or add exact includes and sending IPs.
+all~all-all
Safer rollout choices
Choose ~all while validating senders, then move to -all when your authorized sources are complete.
Record found
Single record
Record valid
Existing record import
Load a domain's current SPF record before extending it so existing authorized senders are preserved.
DNS lookups
7 / 10
Void lookups1 / 2
Live nested lookup count
Check the DNS lookup count across nested includes while editing, before publishing the generated record.
No loops
No duplicates
No empty includes
Cleaner SPF structure
Review duplicate and empty sender entries before copying the generated record into DNS.

SPF record generator FAQs

Answers to common questions about creating, extending, and publishing SPF records.
No. It generates a TXT value you can copy. You still publish the record in your DNS provider.
Yes. Enter your domain, load the current SPF record from DNS, then add includes or IP addresses in the form before copying the updated value.
Publish it on the domain used in SMTP MAIL FROM, often called the return-path or bounce domain. That can differ from the visible From domain. Use @ only when it refers to the correct domain in your DNS provider, and follow your sender's instructions.
No. A domain should have one TXT record that starts with v=spf1. Multiple SPF records cause a permanent error and can make SPF fail.
Use ~all while validating senders if you need a safer rollout. Use -all when you are confident every legitimate sender is included.
Use the exact include domain from your email provider's SPF instructions, such as include:_spf.google.com. Do not invent include domains.
Use them only when your domain's A or MX hosts really send outbound mail. Explicit includes or IP addresses are usually easier to audit.
Yes. It queries live DNS to count nested lookups while you edit the record, before publication. Supply the domain when mechanisms such as a or mx depend on it. After publishing, use the SPF checker to confirm the actual DNS value and count again.

Here's why customers love Suped for DMARC monitoring

MONEYME cover

How MONEYME proactively strengthens domain security and unlocks higher email engagement with Suped

See how MONEYME uses Suped
Jam Cyber cover

How cybersecurity specialist Jam Cyber delivers scalable DMARC protection with Suped

See how Jam Cyber uses Suped
Vision Australia cover

How Vision Australia maintains full DMARC enforcement across a large domain portfolio with Suped

See how Vision Australia uses Suped
The POP Team cover

How The POP Team turns domain checks and DMARC visibility into client ready delivery work

See how The POP Team uses Suped
DigiBean cover

How DigiBean simplified DMARC monitoring and improved email security for their MSP clients

See how DigiBean uses Suped
Alliance Group cover

How Alliance Group moved from reactive guesswork to proactive email management with Suped

See how Alliance Group uses Suped
G2 LeaderG2 Users Most Likely To RecommendG2 Easiest To Do Business WithG2 High PerformerG2 Best Estimated ROI
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing