Skip to content

Email that can't be faked in your name: what a DMARC service does for your business

Quick answer: EasyDMARC is a service that shows who sends email in your company's name and helps you block the senders that aren't yours, without stopping your own mail. As of November 2026 its paid plans start at $44.99 a month ($35.99 a month billed annually) for 2 domains, and it has a free domain scan on its own site.

A customer gets an email that looks like it came from you. It asks them to pay an "updated" invoice into a different bank account. You never sent it, but your name is on it, and the customer's trust in you takes the hit.

This is what a DMARC service is for. Here's what it does in plain words, what it costs, and how I'd roll it out so your real email keeps flowing. I'm an EasyDMARC partner, so I'll say what it's good at and where it's more than you need.

Can someone really send email that looks like it came from my company?

Yes, unless your domain is set up to prevent it. Email was built without a check on who is allowed to write "From: you@yourcompany.com", so anyone can try. Three records published in your domain's settings (called DNS) close that gap:

  • SPF lists the services allowed to send mail for your domain.
  • DKIM adds a signature to each message, so the receiver can tell it wasn't altered and really came from an authorized sender.
  • DMARC tells receiving mail systems what to do when a message fails those checks (nothing, quarantine it, or reject it) and asks them to send you reports about who is sending in your name.

The reports are the valuable part. Without them you are guessing which tools send mail for you. You can see the state of your own domain in seconds with the free domain check on my EasyDMARC tools page.

Is DMARC now required, or just nice to have?

For anyone sending to Gmail or Outlook at volume, it is required; for everyone else it is strongly advised. Per Google's sender guidelines, all senders to Gmail need SPF or DKIM, and bulk senders (more than 5,000 messages a day to Gmail) need SPF, DKIM and DMARC, with the policy allowed to be "none". Microsoft's Outlook rules, effective May 5, 2025, ask domains sending more than 5,000 emails a day to pass SPF and DKIM and publish DMARC, and non-compliant mail goes to Junk.

A small business may sit below those thresholds. The risk of fraud in your name does not depend on your volume.

How would I roll it out without blocking my own email?

In stages, with monitoring first. The order is what protects you:

  1. Inventory. List every service that sends mail as your domain: your mailbox provider, CRM, newsletter tool, invoicing, helpdesk, website forms.
  2. Monitor. Publish DMARC with the policy "none". Nothing is blocked; you only start receiving reports.
  3. Fix. Authenticate every legitimate sender that shows up. Reports usually reveal one you forgot.
  4. Tighten. Move to "quarantine", then to "reject", only when the reports show your real mail passing.
  5. Keep watching. A new tool added next year can break the chain, so the reports stay on.

The classic mistake is jumping straight to "reject" and discovering that your invoices stopped arriving. I always keep a way back: the previous record is saved, so a change can be reversed in minutes.

What does EasyDMARC do, and who is it for?

EasyDMARC collects the DMARC reports, turns them into something readable, and shows which senders pass or fail. According to its pricing page, Premium and above add AI agents, proactive alerts and EasySPF, its tool for managing the SPF record. It fits a business that wants to see and control who sends in its name without learning to read raw report files. If you have one domain and a handful of senders, the free scan and a careful manual setup may be all you need. If you have several tools, several domains or an IT person who dreads this job, a service pays for itself in time.

What it costs: you can start free, and the plans are small next to one fraud incident

As of November 2026, from EasyDMARC's pricing page:

  • The domain scan is free. My tools page checks a domain's DMARC, SPF, DKIM and BIMI records at no charge, and EasyDMARC calls its scanner a free tool.
  • DMARC Plus: $44.99 a month, or $35.99 a month billed annually. 2 domains, 3 months of report history.
  • DMARC Premium: $89.99 a month, or $71.99 a month billed annually. 4 domains, 1 year of history, plus the features above.
  • No per-user fee: the page lists unlimited users on every plan.
  • Larger plans (Deliverability, Enterprise) are priced on request.
  • Trial: Plus and Premium offer a free trial with no credit card required. The page doesn't state its length, so check it when you sign up.

A worked example, with my assumptions stated: one company domain on Plus, billed annually, costs about $432 a year ($35.99 × 12). Assume one fake invoice convinces one customer to pay $5,000 to the wrong account and you spend 20 hours on the fallout at $50 an hour. That's about $6,000 for a single incident. Staged DMARC monitoring doesn't guarantee that never happens, but it closes the easiest route. The realistic alternative is a one-time setup by your IT person or a consultant using free tools; that is cheaper in cash and gives you no ongoing reports.

What traps and safeguards matter?

The main trap is tightening too fast. My safeguards:

  • Start at "none" and tighten only on evidence from the reports.
  • Inventory every sender first, including the ones marketing or finance added without telling IT.
  • Mind the SPF limit: an SPF record may trigger no more than 10 DNS lookups, and piling on services can break it.
  • Save the old DNS records and keep a rollback path.
  • Send test emails from each tool after every change.

Common questions

Will this stop my real email from arriving?

Not if it's done in stages. At "none" nothing is blocked. I only tighten after the reports show every legitimate sender passing.

Does my team have to learn a new system?

No. Your team keeps sending email as usual. Only the person who watches the reports ever opens the dashboard, and that can be me.

What if it doesn't pay off?

The DMARC records live in your own domain, not in EasyDMARC. If you cancel, your SPF, DKIM and DMARC records stay in place; you lose the reporting view, and I'd point the report address elsewhere so nothing is left pointing at a closed account.

Is the free scan enough?

It tells you what's published today. It can't show you who is sending in your name over time. That's what the reports are for.

I set up this kind of protection as part of making business systems work together; see the guide to Zoho CRM integrations for the wider picture. Try the free domain check on your own domain, then tell me what you want to improve.

Disclosure: some links in this article are partner links. If you buy through them, I may earn a commission, at no extra cost to you.