Start with the real requirement
SPF authorizes sending infrastructure for an envelope domain. It can fail after forwarding and has a DNS lookup limit, so adding every imaginable provider is not a sound configuration strategy.
Make the process repeatable
DKIM signs a message using a provider-controlled key associated with a domain. The signature allows a recipient to evaluate whether signed content was changed and whether the key is published correctly.
Manage risk while making changes
DMARC asks whether SPF or DKIM aligns with the visible From domain, and publishes a handling policy. Monitoring before strict enforcement helps identify legitimate senders that need adjustment.
A practical example
For example, a company may send mail from Microsoft 365 and a separate business application. Both need considered authentication; fixing the mailbox provider alone leaves the application unresolved.
Conclusion
Treat authentication as maintained configuration. Revisit it when sending providers change, and verify real message headers rather than relying solely on dashboard checkmarks.
Use this guidance as a planning aid rather than a promise of a particular outcome. Technical decisions depend on the environment, available access and existing safeguards. When requesting assistance, describe the business goal and confirm the service scope before work begins.