Email Security for Businesses: SPF, DKIM and DMARC Explained
By ATTPL IT · · 3 min read

Criminals often send fake emails that appear to come from a real company, asking customers to pay into a new bank account or click a link. Three DNS records, SPF, DKIM and DMARC, let receiving mail servers check whether an email really came from your domain. They also help your genuine emails land in the inbox instead of spam.
1. SPF: who may send
The Sender Policy Framework record lists the servers allowed to send email for your domain, such as your email provider and any billing or marketing tool. Keep one SPF record per domain and include every service that sends on your behalf.
2. DKIM: proof the message is genuine
DomainKeys Identified Mail adds a digital signature to each outgoing email. The receiving server checks it against a public key in your DNS. Most business email providers generate the DKIM key for you; you add it to DNS and switch it on. Setup steps for business email are in our domain and business email guide.

3. DMARC: what to do with failures
DMARC tells receivers what to do when an email fails SPF and DKIM checks, and sends you reports. Start with a monitoring policy (p=none), read the reports to find all legitimate senders, then move to quarantine and finally reject.
4. A safe rollout plan
- List every system that sends email in your name
- Publish or correct SPF
- Enable DKIM for each sending service
- Publish DMARC at p=none with a reporting address
- Review reports for a few weeks, fix gaps, then tighten the policy
5. Signs your domain is being misused
Many businesses discover spoofing only when a customer calls to ask about a strange payment request. Watch for these warning signs:
- Customers or vendors receive invoices or bank change requests you did not send
- Bounce messages arrive for emails your team never wrote
- Your genuine emails start going to spam at large email providers
- DMARC reports show sending servers you do not recognise
If you see these, inform customers through a trusted channel, check mailbox security, reset passwords and enable MFA, and tighten your DMARC policy once legitimate senders are covered. Report cyber fraud on the national cyber crime portal or helpline 1930. Keep a list of everyone authorised to change DNS records, because the same access can also be used to break email.
6. People still matter
Technical controls stop spoofing of your own domain, but not look-alike domains. Train staff to verify payment changes by phone, as covered in our phishing awareness guide, and protect mailboxes with MFA. ATTPL IT Solutions can audit and configure your email domain. For a discussion about your requirement, contact ATTPL HOLDCO or call toll-free 1800-890-0815.
Frequently asked questions
Will DMARC stop all phishing?
No. It stops direct spoofing of your domain; look-alike domains and compromised accounts need other controls.
Can a wrong DMARC policy block my own emails?
Yes, which is why you begin with p=none and monitor before enforcing.
How do I check my records?
Your email provider’s admin console and free DNS lookup tools show whether SPF, DKIM and DMARC are published correctly.
Sources
This article is general information, not professional advice. Rules, rates and schemes change; please check the official sources and consult a qualified professional.


