Sender Policy Framework (SPF) Does the domain needs to be public?

I have been studying a lot within HubSpot, Google WorkSpace and Wordpress and I know my DNS updates comply with general recommendations. I have been successful with reaching my contacts that have email accounts in Gmail, Outlook, iCloud, but not with Yahoo. My rollout of Sender Policy Framework (SPF), DKIM and Dmarc are according every recommendation but some emails are getting Sender Policy Framework (SPF) failure, but they arrive into other providers and I saw that Gmail for example does not denies Dmarc as they requires meeting one of either:

SPF (or SPF alignment)

DKIM (or DKIM alignment)

And my DKIM is passing.

Since I have no idea what I did wrong with Sender Policy Framework (SPF), my question is does the domain needs to be public? I have it right know private, as I have been updating somethings, but I have not being able to identify is going public is a requirement.

If you happen to know, let me know. I have a small business and it is me only, no budget to hire a consultant of dmarc protocols and rollout. My alignment are set as relax as I saw HubSpot requires. I have been also comparing my raw messages with HubSpot users I admire, and are the same. Only other difference is that I have a Starter membership, does that affects? Do I need to upgrade HubSpot membership and set domain as public in order to solve the issue? Or I need to quit reaching out my Yahoo contacts? Is the only provider sending emails into spam and showing Sender Policy Framework (SPF) failure.

Hey @yosoyanais just to confirm do you have all of your spf & dmarc email sending information setup within your HubSpot domain manager? IE: does it say everything is configured correctly within HubSpot?

It’s important to note that, while this is great practice and will help to minimise the amount of undelivable emails you’ll see, it is not a gurantee all emails will be delivered. You still have to maintain your domains email sending reputation.

The SPF and Dmarc records essentially just fully authorise HubSpot’s email sending servers to send emails on behalf of your domain. This doesn’t improve your domains email sending reputation. For example, if you sent out thousands of emails that weren’t opened by anyone, your domains reputation will drop, regardless of any DNS settings you set. This will cause more email receiving systems to reject emails from your domain, regardless of what system you send these emails from.

Emails aren’t 1 to 1, so if you saw another company send the exact same email as you, you won’t see the same results as both domains have different reputations.
If you’re sending a lot of emails to a lot of people who are not engaging, you’re going to destroy your domains reputation. I would focus on cleaning out your database to only have people who are warmed up and engaged. Then focus on rebuilding your domain reputation through a warm up campaign and re-engage your contacts.
If you’re seeing specific errors with SPF setup or email deliverability though please pass them on and I’ll be happy to troubleshoot!

@TomM2 Thanks for your fast response.

Both spf & dmarc email sending information are in fact setup within my HubSpot domain manager. When I did it, followed instrucions and no errors were identified.

I just started to send emails and my list only have 42 persons and about 13 engaged who open. I followed the instructions for those who were hard bounced as full mailbox. I am executing nurturing emails twice a week to keep monitoring engagement but also performing efforts to grow list. I do not think at this point I have reputation as I just started.

Thanks for providing your helpful insights, I appreciate it. Will review more ways of building reputation.