Skip to content
Home/Blog/DMARC, SPF and DKIM Explained for Professional Services F...
Guides

DMARC, SPF and DKIM Explained for Professional Services Firms

If someone can send email that looks like it came from your practice, they can redirect a settlement, change invoice bank details or trick a client into handing over documents. That is domain spoofing...

Call (07) 5619 6555

If someone can send email that looks like it came from your practice, they can redirect a settlement, change invoice bank details or trick a client into handing over documents. That is domain spoofing, and it sits behind a large share of business email compromise cases.

DMARC, together with SPF and DKIM, is how you tell the world's mail servers which messages are really from your domain and what to do with the rest. This guide explains SPF, DKIM and DMARC in plain English for law, accounting, medical and real estate firms, what p=none, quarantine and reject mean, a sensible rollout path, and the bulk-sender rules from Google, Yahoo and Microsoft.

The three records, in one picture

Think of outbound email authentication as three DNS records working together:

Record Job in plain English
SPF Lists which mail servers are allowed to send mail for your domain
DKIM Adds a cryptographic signature so receivers can check the message was not altered and was signed by your domain
DMARC Says what receivers should do when SPF/DKIM fail alignment, and where to send reports

SPF is defined in RFC 7208. DKIM is defined in RFC 6376. DMARC is defined in RFC 7489. You publish them as TXT records in DNS. The DMARC record lives at a hostname of _dmarc on your domain (for example _dmarc.yourfirm.com.au).

SPF: who is allowed to send as you

SPF (Sender Policy Framework) publishes the IP addresses and services allowed to send mail for your domain. Typical entries include Microsoft 365, Google Workspace, a practice management mail relay, and marketing platforms you actually use.

SPF alone is not enough. It checks the "envelope" sender used during SMTP, which is not always the From address your client sees. Attackers can still craft messages that look like your firm unless DKIM and DMARC alignment are in place.

DKIM: a signature on the message

DKIM (DomainKeys Identified Mail) signs selected headers and the body with a private key. Receiving servers fetch your public key from DNS and verify the signature. If the message was tampered with in transit, verification fails.

For Microsoft 365 tenants, DKIM is configured in the Defender or Exchange admin experience and published as CNAME records pointing at Microsoft's keys. Third-party senders (newsletters, scanners, CRM) often need their own DKIM selectors on your domain or a subdomain.

DMARC policy: none, quarantine and reject

DMARC ties SPF and DKIM to the visible From domain. A message "passes DMARC" when at least one of SPF or DKIM passes and aligns with the From domain (as described in RFC 7489). Your DMARC policy then tells receivers what to do when that check fails.

What p=none, quarantine and reject mean

A DMARC TXT record includes a p= tag:

  • p=none — monitor only. Receivers still deliver the message as they normally would, but you get reports. Use this to learn who sends as your domain.
  • p=quarantine — ask receivers to treat failing mail as suspicious (often the junk folder).
  • p=reject — ask receivers to refuse failing mail.

You can also set a percentage with pct= while you tighten policy, and you should set rua= (and optionally ruf=) so aggregate reports arrive somewhere your IT provider monitors.

Example DMARC TXT record

Host/name: _dmarc

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourfirm.com.au; fo=1

That example starts in monitor mode and requests aggregate reports. Replace the mailbox with one you control, or a reporting service your provider uses. Move to quarantine and then reject only after reports show legitimate mail is aligned.

Why professional firms need this

Invoice fraud and settlement redirection often start with a forged "from your firm" or "from your client" message. Without DMARC at enforcement, mailbox providers have little instruction to block lookalike mail using your domain. With DMARC at reject, unauthenticated use of your domain is much harder.

DMARC does not replace staff training or MFA. It closes a specific hole: strangers sending as @yourfirm.com.au. Pair it with the controls covered in Microsoft 365 security gaps and awareness of phishing-as-a-service tooling.

Google, Yahoo and Microsoft bulk-sender rules

Large mailbox providers now expect authentication for senders that reach consumer inboxes at volume.

Google (Gmail personal accounts). Google's Email sender guidelines require all senders to set up SPF or DKIM (among other rules). Senders of 5,000 or more messages per day to Gmail accounts must use SPF and DKIM, publish DMARC (policy may be p=none), keep spam rates low, and meet one-click unsubscribe rules for marketing mail. Requirements took effect from 1 February 2024.

Yahoo. Yahoo's Sender Best Practices state that from February 2024, bulk senders must implement SPF and DKIM, publish a valid DMARC policy of at least p=none with DMARC passing, keep spam complaints below 0.3%, and support easy unsubscribe for marketing mail. Yahoo does not publish a numeric bulk threshold in that guidance.

Microsoft (Outlook.com). Microsoft's Outlook.com Postmaster policies say that from 5 May 2025, domains sending more than 5,000 emails per day to Outlook.com must comply with SPF, DKIM and DMARC. Non-compliant high-volume mail is sent to junk and may later be rejected with SMTP error 550 5.7.515. Microsoft Support's 550 5.7.515 guidance confirms SPF and DKIM must pass, a DMARC record must exist (at least p=none), and messages must pass DMARC validation with alignment to the From domain.

Even a modest professional firm can hit volume thresholds when counting newsletters, portal notifications and day-to-day mail together. Getting SPF, DKIM and DMARC right protects deliverability as well as brand trust.

A sensible rollout path

  1. List every sender. Microsoft 365 or Google Workspace, scanners, practice software, marketing tools, accountants' bulk mail, booking systems.
  2. Fix SPF. One SPF TXT record per domain, including every legitimate sender. Stay within SPF's DNS lookup limits.
  3. Turn on DKIM for your primary mail platform and major third parties.
  4. Publish DMARC at p=none with rua= reporting. Watch reports for two to four weeks.
  5. Align stragglers. Move leftover tools to authenticated senders or stop them using your apex From domain (subdomains can help).
  6. Raise policy to quarantine, then reject, once legitimate mail passes consistently.
  7. Review after changes. New CRM or newsletter tools break SPF/DKIM if nobody updates DNS.

Your Microsoft 365 specialists or cybersecurity services provider should own the DNS changes and the report review, not leave them as a one-off ticket.

Frequently asked questions

What is DMARC?

DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email authentication policy published in DNS. It tells receiving servers what to do when mail claiming to be from your domain fails SPF or DKIM alignment, and it provides reporting so you can see who is sending as you.

Do I need SPF, DKIM and DMARC, or just one?

You need all three for proper protection and for most bulk-sender rules. SPF and DKIM authenticate mail in different ways. DMARC requires alignment with the From domain and sets the policy receivers apply on failure.

What does a DMARC policy of p=none mean?

p=none is monitor mode. Receivers do not quarantine or reject mail based on DMARC failure alone, but you receive aggregate reports. It is the safe starting point before moving to quarantine or reject.

Where is the DMARC record published?

DMARC is published as a DNS TXT record at _dmarc on your domain, for example _dmarc.yourfirm.com.au. The name _dmarc is why people search for that exact string when checking configuration.

Do Google and Yahoo require DMARC?

For bulk senders, yes. Google requires DMARC (policy may be p=none) for domains sending 5,000 or more messages per day to personal Gmail accounts. Yahoo requires bulk senders to publish a valid DMARC policy of at least p=none with DMARC passing. Microsoft applies similar SPF, DKIM and DMARC expectations for high-volume senders to Outlook.com from 5 May 2025.

Will DMARC stop all invoice fraud?

No. DMARC makes it much harder for attackers to spoof your exact domain. It does not stop lookalike domains, compromised mailboxes or social engineering. Combine it with MFA, staff training and verified payment-change processes.

Next step

If your firm has never published DMARC, or it has sat on p=none for years without review, a short authentication audit is the practical starting point. Xen IT works with professional services firms of 6 or more staff across the Gold Coast and Queensland. Request a free IT assessment and we will check SPF, DKIM and DMARC against your real senders and outline a path to enforcement.

Sources

  • IETF, RFC 7489 (DMARC): https://datatracker.ietf.org/doc/html/rfc7489
  • IETF, RFC 7208 (SPF): https://datatracker.ietf.org/doc/html/rfc7208
  • IETF, RFC 6376 (DKIM): https://datatracker.ietf.org/doc/html/rfc6376
  • Google, Email sender guidelines: https://support.google.com/a/answer/81126
  • Yahoo Sender Hub, Sender Best Practices: https://senders.yahooinc.com/best-practices/
  • Microsoft Outlook.com Postmaster, Policies: https://postmaster.outlook.com/policies.aspx
  • Microsoft Support, Fix NDR error 550 5.7.515 in Outlook.com: https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com
  • Microsoft Learn, How email authentication works in Microsoft 365: https://learn.microsoft.com/en-us/defender-office-365/email-authentication-about

Related Reading

Category: Security Published: November 2026 Read time: 8 minutes Author: Xen IT Team
Keep reading
Google Reviews

Don't take our word for it.

★★★★★
Google
“Xen Technologies. We called Xen in to review our cyber security and sort out general IT issues we were having. Laine was exceptional in doing just that. He brought to our attention several issues that needed actioning straight away. In a …”
T
The Bardo Health and Wellness Retreat
Google review · 9 months ago
★★★★★
Google
“Laine is one of the best guys in the industry, I'd highly recommend him and Xen Technologies!”
M
Mikel Real
Google review · 5 months ago
★★★★★
Google
“Laine and his team are the absolute best. Would highly recommend them to everyone”
B
Beth De Laurence
Google review · 5 months ago
★★★★★
Google
“Laine is so easy to work with, great communication. Highly recommend.”
T
Tani Bloudell
Google review · a year ago
★★★★★
Google
“There is nothing more reassuring than having Xen Technolgies as our IT support. They are professional and reliable, problem solved in a short period of time ... highly recommend.”
F
Fat Hen Creek Campground
Google review · 3 years ago
★★★★★
Google
“Xen provided IT assistance for my business. They were prompt, professional and extremely knowledgeable. They cut through several frustrating issues with ruthless efficiency.”
B
Baker Family
Google review · 3 years ago
★★★★★
Google
“Great local msp provider. Matt and the team helped us secure our business.”
G
Greg Tosc
Google review · 4 years ago
★★★★★
Google
“Great company excellent work”
B
Brady's Softwash
Google review · a year ago
Read all reviews on Google →
Free IT assessment

Ready to stop fighting your IT?

Request a free, no-obligation IT assessment. We'll identify your biggest vulnerabilities and opportunities, and give you a clear roadmap, whether you engage us or not.

Prefer to talk? Call us directly
(07) 5619 6555
Suite 8 (West Wing), 2 Fortune Street, Coomera QLD 4209
Tell us about your business

Required

Number of staff (optional)
We'll reply within 2 business hours. No long-term lock-in.
We use your details only to reply to your enquiry. See our privacy policy.