If your organization is troubleshooting email deliverability or your IT team has questions about email authentication, this article explains how Apricot handles SPF, DKIM, and DMARC — and how you can verify that emails sent from Apricot are passing authentication checks.

Apricot uses multiple systems to send emails, including email triggers, Connect emails, and system emails like password resets. Email authentication is managed internally by those sending systems — which means Apricot does not provide SPF or DKIM DNS records to customers, and does not support custom SPF, DKIM, or DMARC configuration.

The good news: you can still verify that Apricot emails are passing authentication checks on your end.

To confirm that emails sent from Apricot pass SPF, DKIM, and DMARC checks, review the email headers for a message sent from the platform.

Send an email from Apricot to yourself using the method you want to verify — an email trigger, a Connect email, or a system email like a password reset.

Open the email in your inbox and access the full message headers. Depending on your email provider, this option may appear as "View original," "Show source," or "View headers."

In the headers, look for these lines:

If you see these, the email passed all three authentication checks.

Note: Results can vary depending on the type of email sent and your organization's email provider.

For a deeper look at how to read email headers and interpret authentication results, visit Cloudflare's guide to DMARC, DKIM, and SPF and scroll to the section "How to check if an email has passed SPFm DKIM, and DMARC."

If you're experiencing ongoing email deliverability problems, contact Apricot Support. A support agent can investigate specific cases and help you identify what's happening.

Important: Please keep in mind that requests for SPF records, DKIM keys, or DNS configuration details fall outside of what Apricot can provide.