The Sender Policy Framework (SPF) validation method was created in order to detect email spoofing. It works simply by checking if a sender is allowed to send emails on your behalf. By adding Phishing Tackle to your SPF records you enable us to send simulated phishing emails on your behalf and reduce the chances they will be marked as spam.
You must first disable return-path headers in your account settings for this guide to work correctly. See this guide to learn how to do so.
Add the information below to your domain's SPF record to allow Phishing Tackle's mail servers to send emails on your behalf:
An example of the SPF record in use with a soft fail (using GSuite as the mail server) would be as such:
v= spf1 include:_spf.google.com include:mail.tacklephishing.com ~all
How to bypass the 10 DNS lookup limit in SPF records
If you find you have reached the DNS lookup limit you will need to add Phishing Tackle's IP address to your SPF record. Our list of IP addresses can be found here.
An example of the SPF record with a soft fail on Phishing Tackle's mail server (using GSuite as a mail server) is as follows:
v=spf1 include:_spf.google.com ip4:184.108.40.206 ~all
We recommend sending a test phishing email (which spoofs your domain) to a single recipient (or small group of recipients) after updating your SPF records.
Whitelisting can be complicated so if you require any further assistance, please contact our support team by clicking here.