The first port of call would be to implement an SPF record for your domain. An SPF record is a DNS record on your domain, which confirms which servers can send email for your domain.


When you send emails, the SPF record is often checked to confirm that your message has come from our server - if it doesn't, then the email can be flagged as spam, or be rejected alltogether.

More often than not, if you don't have an SPF record in place, email providers will treat your emails as more risky, so may put your emails into the Junk/Spam folder.


You can use the SPF wizard in cPanel, under Email -> Authentication to enable SPF for your domain. If your website and email are hosted on our server, then pressing 'Enable' will be all you need to do, as it will generate the correct SPF record for you.

However, if your email is hosted elsewhere, like Office 365 or Gmail, then you would need to add the SPF record that the email provider recommends.


If your email is hosted elsewhere and you are unsure how to proceed, please contact your email provider or us before making any changes, as enabling the default SPF record when your email is hosted elsewhere could worsen the problem.


This is often enough to resolve the issue, however you could also consider enabling DKIM, which is another method that email servers use to verify if emails have come from the correct server. DKIM works by adding a hidden key to all emails you send. If another server tried sending emails from your domain, it would be missing this hidden key, as only our server knows the key. So the absense of the key would allow email providers to determine that the message is risky. But having DKIM in place prevents this and often prevents your messages being flagged as junk/spam.


The same applies in that if your site and email are hosted by us, then you can simply press Enable on DKIM on the Eemail -> Authentication page and our system will do the rest.

However if your emails are hosted elsewhere then you must not enable DKIM using this page, you'd need to add the DNS record provided by the email provider instead. Enabling DKIM using this page when your email is hosted elsewhere could cause your emails to be rejected by email providers.


If your email is hosted elsewhere and you are unsure how to proceed, please contact your email provider or us before making any changes, as enabling DKIM when your email is hosted elsewhere could worsen the problem.

Add to Favourites
Print this Article