Sending Domain Validation
In order to maximize deliverability and help ensure your messages reach the inbox of your recipient, we fully support SPF, Sender ID and DKIM (Domainkey) authentication. These authentication mechanisms are broadly used by ISPs to help validate that your domain (and you!) are sending emails and not a malicious actor. Read more about authentication and deliverability.
Step 1. Email Verification Manager
Step 2. Add your Sending Addresses
After the desired email addresses are added, simply click "Add Address". LeadFWD will perform its first level of authentication and that's to validate that there is a valid MX record associated with your domain. That basically tells our platform that there is a mail server accepting mail for that domain, which is a key component for CAN-SPAM compliance.
Step 3. Authenticate
By default LeadFWD handles SPF authentication at the envelope-handler level, because that validation is performed against our headers and mail infrastructure.
To authenticate Sender ID you will also need to add an SPF record to your DNS zone. It can be confusing, but essentially the Sender ID framework also operates using SPF records but the difference is that they authenticate against the from address and not the envelope-handler (which is where bounces go). So even though we are providing SPF authentication by default, you still need to add an SPF record (we provide the format) to your DNS zone in order to authenticate for Sender ID.
The final and perhaps most critical authentication method is Domainkeys (DKIM). With DKIM we provide you with an encrypted private key that is unique to your sending domain. The private key needs to be added to your DNS zone (TXT record) and each time an email is attempted to delivery an ISP can check the private key in your DNS zone against a unique signature that we added to emails that we send on your behalf. If the key and signature authenticate, then the ISP knows that email is both authorized by the domain that's listed as the sender and also that it hasn't been tampered with in route to the inbox.