Plenty of established Indian businesses still send quotations from addresses like sharmatraders1998@gmail.com. It works, and customers who know you will reply. But a new client, a procurement team at a large company, or a bank's onboarding desk will look at that address and quietly wonder whether you are a serious supplier. And because anyone can create a similar-looking Gmail address in a minute, it is also easy for a fraudster to impersonate you.
This guide explains why a domain email ID matters, how to set one up correctly, and the three DNS records, SPF, DKIM and DMARC, that stop others sending email in your company's name.
Why does a domain email ID matter?
- Trust. accounts@yourcompany.in tells the reader the email comes from an organisation that owns its name. It matches your website, invoices and visiting cards.
- Control. The company owns the mailbox, not the employee. When someone leaves, you disable their account and keep the mailbox, instead of losing years of customer correspondence that sat in their personal Gmail.
- Deliverability. Large mailbox providers now expect proper authentication. Google's sender guidelines, which took effect on 1 February 2024, require every sender to set up SPF or DKIM, and require bulk senders (more than 5,000 messages a day to Gmail accounts) to set up SPF, DKIM and DMARC. You can only configure these for a domain you own.
- Protection against spoofing. With DMARC in place, mail servers can reject messages that pretend to come from your domain but did not.
How do you set up a domain email ID, step by step?
- Own the domain in the company's name. Check the registrar account. If it is registered under a web designer's personal account, transfer it now. Use a company email and enable two-factor authentication on the registrar.
- Choose an email provider. Google Workspace and Microsoft 365 are the common choices; both give proper spam filtering, mobile apps and admin controls. Free email bundled with cheap shared hosting is usually a false economy: weaker spam filtering, poor deliverability and no proper admin console.
- Verify the domain with the provider by adding a TXT record in DNS.
- Add MX records so incoming mail goes to the provider. Remove old MX records from the previous host.
- Create mailboxes for people (firstname@) and shared aliases or groups for functions (sales@, accounts@, support@). Functional addresses survive staff changes.
- Migrate old mail from personal Gmail or the old host using the provider's migration tool, if needed.
- Set up SPF, DKIM and DMARC as below.
- Enforce two-factor authentication for every account. A compromised mailbox is a common starting point for invoice fraud.
SPF, DKIM and DMARC explained without jargon
| Record | What it does | Analogy |
|---|---|---|
| SPF | Lists which servers are allowed to send email for your domain | A list of authorised couriers |
| DKIM | Adds a cryptographic signature to each message, proving it was not altered and came from an authorised system | A tamper-proof seal on the envelope |
| DMARC | Tells receiving servers what to do if SPF or DKIM fails, and sends you reports | Instructions to the receptionist: reject parcels without the seal |
SPF
A single TXT record on your domain listing every service that sends mail as you: your email provider, plus any others such as your CRM, billing software, website contact form or newsletter tool. Common mistakes are having two SPF records (only one is allowed), forgetting the billing software that sends invoices, and ending with a permissive "+all".
DKIM
Generate the DKIM key in your email provider's admin console, publish it as a DNS record, then switch signing on. Do the same for every third-party service that sends on your behalf; most provide their own DKIM records.
DMARC
Start in monitoring mode with a policy of p=none and a reporting address. Google's guidelines state that a DMARC policy of none is acceptable for bulk senders, but none only monitors; it does not stop spoofing. For a domain to pass DMARC, the From address domain must align with the domain that passed SPF or DKIM.
A safe rollout:
- Weeks 1 to 4: p=none. Read the reports (a DMARC report viewer makes them readable) and find every legitimate service sending as your domain.
- Fix SPF and DKIM for each legitimate sender until they pass.
- Move to p=quarantine, so failing messages go to spam.
- Move to p=reject once you are confident. Now spoofed mail claiming to be from your domain is rejected by receivers that honour DMARC.
Why does this matter for fraud in India?
A classic scam targets your customers: a fraudster sends an email that appears to come from your accounts team, saying "our bank account has changed, please pay this invoice to the new account". If your domain has no DMARC enforcement, that email can land in the inbox looking genuine. With DMARC at reject, exact-domain spoofing is blocked, so fraudsters must fall back to look-alike domains (yourcompany-in.com), which careful readers can spot.
Spoofing and phishing are serious enough that CERT-In's April 2022 directions list "identity theft, spoofing and phishing attacks" among the incidents body corporates must report to CERT-In within six hours of noticing them. Prevention is far cheaper.
Also protect against the other side: tell customers in writing that you will never change bank details by email alone, and verify any such change from a supplier by phone on a known number.
Other settings worth getting right
- PTR and TLS: Google's guidelines also require valid forward and reverse DNS for sending servers and TLS for transmission. Major providers handle this; self-hosted mail servers often do not.
- One-click unsubscribe for marketing email, a requirement for bulk senders under Google's guidelines, along with a visible unsubscribe link.
- Separate domain or subdomain for bulk marketing (for example news.yourcompany.in), so a marketing campaign's reputation problems do not affect invoices and quotations.
- Spam rate: keep it low. Google's guidelines set a hard limit of 0.3% in Postmaster Tools and recommend staying below 0.1%.
Quick checklist
- Domain registered in the company's name with two-factor login at the registrar.
- Business email provider with all staff on company accounts.
- Exactly one SPF record covering every sending service.
- DKIM enabled on the provider and every third-party sender.
- DMARC moving from none to quarantine to reject.
- Two-factor authentication enforced for all mailboxes.
- A written "we never change bank details by email" notice to customers.
How Cehpoint can help
We can set up business email on your own domain, migrate old mail, configure SPF, DKIM and DMARC, and take DMARC to enforcement without blocking legitimate invoices, as part of an engagement under our IT consulting service. If your concern is phishing and impersonation more broadly, see our cyber security service, or start with the free security self-check.