| alert-warning | Starting February 1, Gmail may reject emails from domains with unverified SPF records. Set your SPF records to ensure your emails reach recipients' inboxes and don't land in spam. |
Titan is focused on ensuring high deliverability of emails for our users and SPF records play an important role in it. Here are some more details about SPF records and their role in email delivery:
- What are SPF Records?
- Why are SPF Records required?
- How can SPF record Impact Email Delivery?
- Add SPF records for Titan
What are SPF Records?
Sender Policy Framework is an email authentication method designed to detect forging sender addresses during the delivery of the email. SPF alone, though, is limited only to detect a forged sender claimed in the envelope of the email which is used when the mail gets bounced.
Why are SPF Records required?
SPF records are used to prevent spammers from spoofing your domain name. Recipient servers can use the SPF record you publish in DNS to determine whether an email that they have received has come from an authorized server or not.
They can then make a decision about how to treat that email. Over recent years SPF has gone from a “nice to have” to a “must-have”. Even if they aren't perfect, they are quite effective and are part of being a good email citizen on the internet.
Major email inbox providers (like Gmail and Yahoo) have mandated stronger authentication starting February 2024. To ensure that your emails to Gmail and Yahoo recipients are not going into their spam folders, please set up the correct MX and SPF records for your domain.
How can SPF record Impact Email Delivery?
In the case of SPF, its chief role is to prevent email spammers from using your domain and sending “spoof” emails. SPF records prevent spammers from sending messages with bogus From addresses attached to your domain. This stuff gets fairly technical, but let's keep it simple for now.
Have you ever received one of those nonsense emails that looks like it is being set out from a user posing to be someone else, but is actually from a spammer posing as a known user at your end? This is called a "spoof" email because it's quite easy to fake the domain associated with an email (like the spammer in this case). SPF was created to combat these sorts of fake sender issues.
Unless you set up an SMTP configuration, Titan sends emails on your behalf when you reply to a customer. For the sake of illustration, let's say your mailbox address is support@domain.com. When you reply to a customer and the email goes out, the customer's server will ask the following questions:
- Who sent this email?
- Does the sender have permission to send on behalf of this domain?
In our example, the "who" is support@domain.com and the "sender" is Titan. Without an SPF record specifying Titan as an approved sender, it's likely your email will be marked as spam. If there is an SPF record that includes Titan as an approved sender, then it's virtually guaranteed to skip the spam filter. That's why this is so important!
Add SPF records for Titan
- Navigate to the DNS / Domain Management Page/ DNS Control Panel in your admin page
- Find the TXT Records/ Email Servers/ Email Settings option
- Add OR Replace the following TXT records to your domain
- Set the Name/ Host field as either @ or leave it Blank.
- Set the Value field as v=spf1 include:spf.titan.email ~all
- Set the TTL value to 1 hour or 3600 seconds.
Note: You should set the record type to "TXT" rather than "SPF", as the SPF record type is deprecated as per as RFC and is no longer supported.
| Record Type | Host | Value | TTL |
| TXT | @ | v=spf1 include:spf.titan.email ~all | 1 hour/ 3600 seconds |
That's it! Your SPF records are all set now. Feel free to reach out to us at support@titan.email for any queries regarding SPF records, we'll be happy to help you!