Align your audits with your branding by using a custom email address.
When Insites sends an email, the default address is email@example.com. However, if you are white-labelling Insites or using our lead generation feature, you may want to have these emails sent from your own address, e.g. firstname.lastname@example.org instead.
In order to set this up correctly, you'll need to set some DNS records so that we're authorised to send emails on your behalf, and so that they don't end up in your clients' spam folders.
What is DKIM?
DKIM, or DomainKeys Identified Mail, is an email authentication method that uses a digital signature to let the receiver of an email know that the message was sent and authorised by the owner of a domain.
Once the receiver determines that an email is signed with a valid DKIM signature it can be confirmed that the email's content has not been modified. In most cases, DKIM signatures are not visible to end-users, the validation is done on a server level.
How can I do it?
First off you provide us with a white-labelled email address to send your reports out from. We'll then start the verification process and provide you with three CNAME records to add to your domain name
You’ll provide us with a white-labelled (custom) email address to send your reports out from
We'll then start the verification process and we will provide you with three CNAME records to add to your DNS configuration
You add these DNS records, wait for up to 48 hours for the details to propagate and then it is complete!
It’s as simple as that! Once the verification process has been completed, this email address can be used for all outgoing emails from your Insites account.
What is SPF?
Sender Policy Framework (SPF) is an email validation standard that's designed to prevent email spoofing. Domain owners use SPF to tell email providers which servers are allowed to send email from their domains. SPF is defined in RFC 7208.
How can I do it?
Your current SPF record, if you have one, will be a DNS TXT record that looks something like this, where myemailprovider.com should be the organisation that provides your email service:
v=spf1 include:myemailprovider.com ~all
You need to add in AWS SES (our email provider) to this, so the rule looks something like this:
v=spf1 include:myemailprovider.com include:amazonses.com ~all
Once you've amended this DNS record you're good to go!