Skip to main content
All CollectionsGeneral
SPF and Sender Authentication
SPF and Sender Authentication

Understanding SPF and sender authentication is crucial for safeguarding your email communication. Learn how to implement these protocols.

Updated over a week ago

Sender Policy Framework (SPF) is a crucial tool in safeguarding domain names from email spoofing by enabling domain owners to declare the authorized sources for their emails. This guide walks you through the steps to configure SPF with Recruitly for enhanced sender authentication.


Domain with Existing SPF Record:

If your domain already has an SPF record (commonly added during services like Microsoft 365 or Google Business setup). You need to edit your existing TXT record and add the following value:

include:spf.protection.recruitly.io


Domain without SPF Record:

If your domain lacks an SPF record then add a new DNS record with the following parameters:

TXT record 
TXT name: @
TXT value: v=spf1 include:spf.protection.recruitly.io ~all


Verifying SPF Configuration:

Use the SPF survey tool from Dmarcian to quickly identify whether SPF is set up correctly and which servers are authorized - https://dmarcian.com/spf-survey/

If Recruitly is correctly included in the SPF record, you should see spf.protection.recruitly.io in the record.

Ensuring the proper configuration of SPF is vital for secure sender authentication. Whether your domain already has an SPF record or needs a new one, the steps outlined above guide you through the process. Utilize the SPF survey tool to confirm the correct setup.

Note:

Tools like Dmarcian might report SPF alignment of 0%, but with DKIM and SPF configured and DMARC policy set to "relaxed" alignment, your emails from Recruitly will be delivered.

Did this answer your question?