Email is where most attacks on businesses begin. A supplier's “updated bank details”, a message from the “managing director” asking for an urgent transfer, or a fake Microsoft 365 or Google login page can cost a company money, data and reputation in minutes. The good news: a handful of settings and habits stop most of these attacks.
How email attacks on businesses work
| Attack | What happens | Main defence |
|---|---|---|
| Spoofing | Email appears to come from your own domain, e.g. accounts@yourcompany.com | SPF, DKIM and DMARC |
| Lookalike domains | yourcompnay.com or yourcompany-in.com used to fool staff and customers | Training, domain monitoring, external-sender warnings |
| Business email compromise | A real mailbox is hacked and used to request payments | Multi-factor authentication, payment verification |
| Credential phishing | Fake login pages steal email passwords | MFA, filtering, awareness |
| Malicious attachments | Invoices or documents that install malware | Attachment scanning, patched devices |
SPF, DKIM and DMARC in plain words
- SPF (Sender Policy Framework): a DNS record listing the servers allowed to send email for your domain – for example Google Workspace, Microsoft 365, Zoho Mail, and your marketing or billing tools.
- DKIM (DomainKeys Identified Mail): a digital signature added to each email, proving it really came from your domain and wasn't changed on the way.
- DMARC: a policy that tells receiving mail servers what to do when an email fails those checks – monitor it, send it to spam, or reject it – and sends you reports about who is sending email using your name.
Step-by-step: securing your domain's email
- List every service that sends email as you: your mailbox provider, website contact forms, CRM, billing or invoicing software, newsletter tools and helpdesk.
- Publish one SPF record that includes all of them. A domain must have only one SPF record – combine entries rather than adding a second.
- Turn on DKIM in each sending service and add the DNS records they give you.
- Start DMARC in monitoring mode (policy “none”) with an address to receive reports.
- Read the reports for a few weeks and fix any legitimate service that is failing.
- Move to enforcement – first “quarantine”, then “reject” – once only your own services pass.
How to check your current setup
You can see where you stand in a few minutes, without changing anything:
- Send an email from your company address to a personal Gmail account, open it, and choose “Show original”. Gmail shows whether SPF, DKIM and DMARC passed.
- Look up your domain's TXT records with your DNS provider or a free online DNS checker, and note whether there is a
record starting with
v=spf1and one at_dmarc.yourdomain. - In your mailbox admin console, check how many users have multi-factor authentication switched on.
If any of these come back missing or failing, that is where to start.
Protect the mailboxes themselves
Domain authentication stops outsiders pretending to be you. It doesn't help if someone steals a real password. For that:
- Multi-factor authentication on every mailbox, starting with finance, management and admins
- Unique passwords and a password manager; no shared logins
- Disable old protocols that bypass MFA where your provider allows it
- Alerts for suspicious sign-ins and new mail-forwarding rules (attackers often add hidden forwarding)
- Removing mailboxes of staff who have left
A simple payment-safety rule
Most email fraud ends with a payment. Make it a written company rule that any new bank account, change of bank details or urgent payment request is confirmed by a phone call to a number you already have – never one from the email. This single habit defeats most invoice and CEO-impersonation fraud, even when the email looks perfect.
Train people with real examples
Short, regular sessions work better than one long annual training. Show staff real examples of lookalike domains, fake login pages and urgent payment requests, explain how to report a suspicious email, and thank people who report – even when it turns out to be genuine. Simulated phishing tests help measure progress.
Common mistakes
- Two SPF records on the same domain, which makes SPF fail.
- Forgetting a sending service, so genuine invoices or form emails start bouncing after DMARC enforcement.
- Leaving DMARC on “none” forever – it reports problems but doesn't stop spoofing.
- MFA only for some users – attackers target the one mailbox without it.
If an email account is compromised
- Reset the password and sign out all sessions; turn on MFA.
- Check for and remove forwarding rules and unknown connected apps.
- Warn customers and suppliers who may have received fraudulent emails.
- If money was sent, contact your bank immediately and report on 1930 / cybercrime.gov.in. Indian organisations should also check their CERT-In reporting obligations.
Tinos sets up and secures business email with correct SPF, DKIM and DMARC, and our cyber security team runs phishing awareness training and email security reviews. Read more about ransomware protection and common online scams.
Frequently asked questions
Will DMARC stop all phishing emails?
No. DMARC stops emails that pretend to come from your exact domain. Lookalike domains and hacked mailboxes need other defences: MFA, filtering, external-sender warnings and trained staff.
Can setting up DMARC block my genuine emails?
It can if you enforce it before every legitimate sending service is set up correctly. That's why you start in monitoring mode, read the reports and only then move to quarantine and reject.
Do small businesses really need this?
Yes. Smaller firms are frequent targets precisely because they often lack these controls, and authentication also helps your genuine emails reach customers' inboxes.
