SPF Record Generator
Build an SPF record locally
Your record will appear here.
What SPF authorises
SPF lets a domain publish which systems may use it in the SMTP envelope sender or HELO identity. It does not authenticate the visible From address by itself. Forwarding can also break an otherwise valid SPF path, which is one reason DKIM and DMARC should be deployed as complementary controls.
Build one record, not several
A domain should publish one SPF policy. Combine authorised services into that record instead of adding a second v=spf1 TXT value. Include only services that really send mail, remove retired senders, and stay within SPF's DNS-lookup limit. The generator creates syntax from the entries you provide but cannot discover forgotten senders.
Worked example
A Google Workspace-only domain commonly begins with v=spf1 include:_spf.google.com ~all. A website platform, helpdesk or marketing service may require another authorised mechanism. Confirm the exact value in each provider's current documentation before publishing.
Authoritative references
Read the underlying standards and provider instructions before changing production DNS: RFC 7208 (SPF), RFC 9989 (DMARC), Google Workspace SPF guidance and your sending provider's current DKIM documentation.
Publish carefully
Always verify generated records against your email provider's official documentation. Never paste private DKIM keys, DNS passwords or API tokens into a public tool.
Editorial responsibility
Published by Acerville Sparks Limited. Software assists research, drafting and automated record testing. Internet standards, provider documentation, reproducible checks and limitations are shown so readers can inspect the work. No independent deliverability consultant review is claimed. Reviewed 4 September 2026.
What this site does not do
No inbox guarantee. No live DNS checks. No storage of entered data. No passwords or private keys requested.