SPF Guru is a free, community-supported tool that allows domain owners to exceed the SPF (Sender Policy Framework) 10-DNS-lookup limitation by using two hostname includes powered by macro-based DNS responses.
SPF Guru is offered on a best-effort basis. While we strive to maintain reliable uptime, accurate SPF resolution, and secure operations, we do not guarantee the availability, accuracy, or continuity of the service. SPF Guru is not intended to be a mission-critical solution and should not be relied upon as the sole method for achieving DMARC compliance on production e-mail systems. The SPF Guru strongly recommends configuring DKIM alongside SPF to best practice for more resilient DMARC compliance.
SPF Guru is provided “as is” without warranty of any kind—express, implied, or statutory—including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be error-free, secure, or uninterrupted.
Under no circumstances shall the creators, contributors, or operators of SPF Guru be held liable for any direct, indirect, incidental, consequential, or special damages, including but not limited to loss of data, loss of business, delivery issues, reputational harm, or legal disputes, arising from the use or inability to use the service—even if advised of the possibility of such damages.
By using SPF Guru, you acknowledge that it is your responsibility to validate the effectiveness of the service in your environment, monitor SPF results, and ensure compliance with your organisation’s security and email delivery policies. You agree not to use SPF Guru for abusive, malicious, or unlawful purposes.
Support for SPF Guru is offered on a best-effort and volunteer basis. If you encounter issues or have feedback, you may log an issue via the public GitHub repository at github.com/smck83/spf.guru/issues or email [email protected]. While we try to respond to all requests, timely responses cannot be guaranteed.
Use of this service implies acceptance of this disclaimer.