Resolving an SPF record not found error

How to resolve an SPF record not found error with your custom domain

Updated this week

Receiving an error when using HoneyBook's domain tester tool indicates that there is an issue with your integrated email's DKIM or SPF configuration, which can significantly impact email deliverability for your custom domain. If you received an SPF record not found error, we'll walk through the steps you can take to fix the issue below.

What this error means

What you'll need to fix it

Where you'll fix it

💡 Your SPF record is not defined and you will need to work with your domain provider to configure it.

Information from your domain provider*

➡️ Your domain provider's management console*

📚 Tip

*Not sure who your domain provider is?

2. Enter your domain name and click Lookup.

  • Tip: If your email address is [email protected], your domain name should be entered as: honeybook.com

3. Scroll down to the Registrar Information section. Your provider will be listed as the Name.

  • Note: If there is a Reseller Information section, your provider will be listed there, not under Registrar.


How to resolve the error

1. First, log in to the management console for your domain provider.

2. Locate the page where you update DNS TXT records for your domain.

3. Click to add a new record.

While the exact process varies by provider, here are resources to define SPF for some of the most common providers:

4. Enter the relevant information for SPF: Type, Name/Host, Value/Data, and TTL.

Field name

Value to enter

Type

TXT

Note: Make sure to select TXT as the type—don't select SPF.

Name/Host

The host or name information from your provider. Here are the name/host values for some of the most common providers:

  • Squarespace: @

  • Google Workspace: @

  • Wix: [Blank]

  • GoDaddy: @

  • Bluehost: @

  • SiteGround: [Blank]

  • NameCheap: @

  • Hover: @

Value/Data

The TXT value.

Here are TXT values for some of the most common providers:

  • Google: v=spf1 include:_spf.google.com ~all

  • Outlook: v=spf1 include:spf.protection.outlook.com -all

  • iCloud: v=spf1 include:icloud.com ~all

  • Zoho: v=spf1 include:one.zoho.com -all

TTL (time to live)

How long the server should cache this information. For example: 1 hour

Example:

📚 Tip

You can verify and validate the SPF record for your domain using this tool.

5. Once you've added the record, remember to save your changes.

📣 Note

While HoneyBook is able to check this record for you and notify you of the error, defining an SPF record is done outside of HoneyBook and directly in your domain provider's Domain Name System (DNS) settings. HoneyBook is not able to complete this process for you.

If you need further assistance, please contact your domain provider's support team.


Next steps

Verify your changes

Once you've made the appropriate changes in your domain provider's DNS settings, you're all set—nothing needs to be done in HoneyBook.

It can take up to 48 hours for DNS changes to take effect. Afterwards, you can always run the deliverability test again to make sure any errors are fixed.

If you send more than 5,000 emails per day

If you send more than 5,000 emails per day, Google and Yahoo's email spam filter updates (taking effect February 2024) impact you directly. Once you've verified your DKIM and SPF configuration, you will also need to define DMARC.

📚 Tip

You can check your DMARC settings using this tool.

Still have questions? Feel free to send us a message by clicking the Question Mark icon on any HoneyBook page. Our team is always happy to help!

Did this answer your question?