A customer says they never got your offer, but you sent it. It is in their spam folder. The most common reason is not the content but that your domain does not prove the message really comes from it. Gmail, Outlook and Yahoo now ask for that proof, especially from business addresses.
The proof is three DNS records: SPF, DKIM and DMARC.
SPF: who may send on your behalf
SPF is a TXT record that lists the servers allowed to send messages from your domain. It looks like this:
v=spf1 +a +mx +ip4:server-IP-address ~all
If a message comes from a server that is not on the list, the recipient treats it as suspicious. A domain may have only one SPF record. If you also send through another service (for example Mailchimp or Google Workspace), its include: goes into the same record, not a new one.
DKIM: a digital signature on every message
DKIM signs every message with a key that only your server has, and the public part of the key is in DNS. The recipient checks the signature and knows the message was not changed on the way and really is from your domain.
DMARC: what to do with fake messages
DMARC tells Gmail and Outlook what to do with a message that claims to be from your domain but fails SPF or DKIM: let it through, put it in spam or reject it. It also protects you from fraudsters sending fake invoices "in your name". Start with a record that only monitors:
_dmarc TXT v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.mk
After a few weeks, once you see your real messages passing, change p=none to p=quarantine, and later to p=reject.
How to set them up in cPanel in 10 minutes
- In the client panel, open the hosting plan and click "Log in to cPanel".
- In the Email section, open Email Deliverability. For each domain you will see whether SPF and DKIM are in order.
- If it says "Problems Exist", click Manage. If the domain uses our nameservers, the Repair button fixes the records automatically.
- If the DNS is with another provider, cPanel shows the exact values. Copy them and add them there as TXT records.
- You add the DMARC record yourself: in cPanel that is the Zone Editor, a new TXT record named
_dmarc; if the DNS is elsewhere, add it there.
Not sure where your DNS is? Read how to connect your domain to hosting.
How to check that it works
Send a message to your own Gmail address, open it, click the three dots and choose "Show original". It should say SPF: PASS, DKIM: PASS and DMARC: PASS. If any says FAIL, the value in DNS does not match the one in cPanel.
If the records are fine but messages still go to spam
- Bulk messages. Do not send newsletters to hundreds of addresses from an ordinary mailbox. Use a newsletter service, with its
include:in your SPF. - Content. An image with no text, shortened links and attachments such as .zip or .exe raise the spam score.
- A new domain. Gmail trusts a new domain less in the first weeks. Start with ordinary correspondence with people who will reply.
- Forwarders. Messages automatically forwarded to Gmail sometimes lose their SPF. It is better to connect the mailbox directly in your app.
If everything is checked and the problem remains, open a ticket with the headers ("Show original") of one message that went to spam and we will check the server side too.







