How To Set Spf Record For My Domain

How to fix SPF Tape

• 5 minutes to read

Before creating the SPF record for your domain, it is of import to find out what the server address for the post service to exist authorized (which is going to be permitted to send emails on your behalf).

In this tutorial, the record will be prepare up for Google Apps. We volition use:

Mailgun as our mail service service (the email service to use to send the email - permitted to send e-mail on behalf of your domain).
Google Workspace domain electronic mail address to "send as" (your 'domain' as the sending email, in other words, what yous meet in 'from' address in your mailings and e-mail).

Annotation

This Google account'south domain is hosted by Enom. Your domain settings and DNS may differ. Please contact your DNS support team for help.

How to create DNS records for Microsoft 365 when you manage your DNS records:

Yous tin can follow the full general instructions from Microsoft for creating DNS records for Microsoft 365.

Open the domain settings for the Google domain

x -screenshot

Open Domains.

x -screenshot

The icon for opening Domains may exist hidden by default and is then found nether More than controls.

x -screenshot

Under Domains, open Add/remove domains.

x -screenshot

Click Advanced DNS settings to see your details.

x -screenshot

Click Sign in to DNS panel to open the DNS console window. Yous may take to sign into this DNS panel with a carve up DNS account.

Add the SPF tape

Go to Host Records in the DNS console. The existing SPF record for your Google account is there by default.
We want to add _spf.online.superoffice.com which contains right records for both Mailgun clusters (EU and US). Since in that location only should exist one SPF record - we demand to combine the existing one with the new one. The actual TXT record to add is "v=spf1 include:_spf.online.superoffice.com ~all".

Annotation

For customers using DKIM (only): you need to add "include:mailgun.org ~all" to be able to send and receive emails. Read more in DKIM setup.
1. Click Edit. Update the existing record (text field) with the new combined record.
2. Click Salve to update the information.

Annotation

Once yous've added the records and they've propagated, it can take 24-48 hours for DNS changes to propagate.

Test a new SPF record

There are several tools available online to test your SPF record. Here nosotros use MX Toolbox.

Open up the SPF tool.
Add together your domain (the one that y'all are going to send our mailings equally) and click SPF Record Lookup.
The issue should show that _spf.online.superoffice.com is included and pass the test for permit.

What's the difference between ~all and -all?

Given many receivers are not actively bouncing mail based on SPF pass/fail, there isn't a strong argument for either -all or ~all in SPF records. For a while, Hotmail was advising that senders who published a -all record would have better commitment. This led to -all became a de-facto standard for a lot of ESPs and bulk senders. More than recently, at that place does non seem to be whatsoever do good to publishing -all fifty-fifty at Hotmail (Outlook.com, live.com, and like).

What should I publish?

We recommend "~all" (soft fail if no matches) vs "-all" (hard neglect if no matches) equally a bourgeois measure. A soft postal service means that the message will exist tagged with a header documenting the failure, but will yet be accustomed. If yous prefer a difficult failure, ie "-all", then feel free to use that instead. There's not a huge do good to publishing -all and sometimes post gets forwarded around. The one time we recommend an -all record is when a domain is getting forged into spam. Domain forgery can crusade a lot of bounces. The number of bounces can be bad enough to accept downwardly a mail server, particularly those with a small user base. Many ISPs volition check SPF before sending back a bounce and and so an -all record tin can decrease the amount of blowback the domain owner has to bargain with.