Hi Nermine,

As a follow-up question, is this domain also being used to send emails outside of Klaviyo, like through Gmail, Google Workspace, or any other platform?

I ask because we recently encountered a similar situation. When testing the domain externally, it appeared that the SPF record was missing, but it turned out that Klaviyo's sending was correctly configured. The issue was actually with emails being sent through Google Workspace, which hadn’t had the SPF properly set up.

If that's the case for you, too, you might need to add or update the SPF record on your DNS to account for other sending services like Gmail, in addition to Klaviyo. Klaviyo support can confirm if their part is fine, but if the DNS is missing entries for other platforms, it would have to be updated at your DNS provider.

If that's not the issue, I recommend contacting Klaviyo Support for further assistance.

Hope this helps!

Propagation time delays with your DNS provider are possible but rare. But if the SPF record was created under a subdomain that also may cause it not to show when you do a lookup on your apex domain. Check/fix the record at the DNS provider to make sure the SPF record is on the apex domain set usually with an “@” or null hostname field. Then check it at mxtoolbox or netbeep.com/help/klaviyo-check

Hi ​@Nermine ,

Thank you for reaching out to the Community! Can you confirm your branded sending domain so I can take a look on my end? 

Thanks for pointing that out  @Obeth,  I checked with the client, and the domain isn’t being used outside of Klaviyo. Really appreciate the insight!