We Checked 104 South African Accounting and Financial Firm Websites: 3 in 4 Can Have Their Email Spoofed
By Next Level Web Solutions · · 10 min read · Accounting and financial firms
The short answer: In November 2026 we checked the public DNS records of 101 South African accounting, tax, audit, financial advisory and insurance broker domains that receive email. 77 of them (76%) have no enforced DMARC policy: 43 publish no DMARC record at all and 34 publish one set to "none", which tells receiving mail servers to do nothing about forged mail. Only 24 firms (24%) publish a policy of quarantine or reject.
What this means in plain English
Email was built without a way to prove who sent a message. SPF, DKIM and DMARC are three DNS records that add that proof. DMARC is the one that tells the world what to do with mail that claims to come from your domain but fails the checks. Without an enforced DMARC policy, a criminal can send an invoice, a "new banking details" notice or a fake SARS deadline reminder that shows your firm's exact domain in the From line, and many mail systems will deliver it.
For a firm that holds client financial records, that is a practical risk and a professional one. This article gives the numbers, explains why the big mailbox providers now care, and walks through a fix you can do yourself.
Key findings
All numbers come from our own scan, described in the methodology section below. Email figures use the 101 domains that publish mail (MX) records. Website figures use the 102 homepages that loaded.
| Check | Firms | Share |
|---|---|---|
| Publishes an SPF record | 93 of 101 | 92.1% |
| Publishes any DMARC record | 58 of 101 | 57.4% |
| DMARC set to p=none (monitor only) | 34 of 101 | 33.7% |
| DMARC set to p=quarantine | 11 of 101 | 10.9% |
| DMARC set to p=reject | 13 of 101 | 12.9% |
| No DMARC record at all | 43 of 101 | 42.6% |
| No enforced DMARC (none or missing) | 77 of 101 | 76.2% |
| SPF present but no DMARC | 40 of 101 | 39.6% |
| SPF plus enforced DMARC | 23 of 101 | 22.8% |
Three things stand out.
First, the basics are mostly there. Nine in ten firms publish SPF, which most email providers set up automatically. The gap is the next step. Forty firms have SPF but no DMARC, which means they did the first step and stopped.
Second, "I have DMARC" is not the same as "I am protected". A p=none policy is a monitoring setting. It is a sensible first week, but one in three firms in our sample appears to have stayed there.
Third, the website side is in better shape than the email side. Every homepage that loaded was reachable over HTTPS, 101 of 102 (99.0%) had a certificate that validated, 100 of 102 (98.0%) declared a mobile viewport, and 89 of 102 (87.3%) redirected plain http addresses to https. Firms have clearly been told to fix the visible padlock. Almost nobody has been told to fix the invisible email records.
A second finding: tracking without a visible consent notice
52 of the 102 homepages (51.0%) loaded a recognisable tracking or analytics script. Of those 52, 35 (67.3%) showed no cookie banner that our scan could detect, and 25 (48.1%) had no privacy, POPIA or PAIA link in the homepage HTML. 19 firms (36.5% of the tracking sites) had neither. Overall, only 54 of 102 homepages (52.9%) carried a detectable privacy link. Because the scan reads raw HTML, banners and links added later by JavaScript can be missed, so treat these as an upper bound on the problem. They are still a prompt to check your own site.
Why mailbox providers now care
Three large providers have made authentication a condition of delivery for high-volume senders, and the direction of travel is clear.
- Google. Since 1 February 2024, Google requires every sender to authenticate with SPF or DKIM, and requires bulk senders (more than 5,000 messages a day to Gmail) to set up SPF, DKIM and DMARC, with the From domain aligned. Google's page says the DMARC policy for bulk senders can be set to none. Unauthenticated mail may be marked as spam or rejected. (Google email sender guidelines)
- Microsoft. From 5 May 2025, Outlook.com, Hotmail and Live.com apply SPF, DKIM and DMARC requirements to domains sending more than 5,000 emails a day, with a DMARC policy of at least p=none. Non-compliant mail from those senders is routed to the Junk folder, and Microsoft has said rejection will follow on a date it has not announced. (Microsoft Defender for Office 365 blog)
A single accounting firm sending a few hundred emails a day is below those thresholds, so these rules do not directly bind it. They matter for two reasons. They show where the whole system is heading, and the checks that apply to bulk senders are the same checks your clients' mail systems use when judging your invoices.
Why it matters for a firm
Spoofed invoices and banking-detail changes. Business email compromise is the pattern where a criminal impersonates a trusted sender to redirect a payment. An ITWeb article by the chief information officer of a South African cyber security company describes fake supplier invoices with changed bank details and urgent payment instructions as typical examples, and notes that these losses are not included in the R2.4 billion SABRIC recorded for digital banking crime in 2025. (ITWeb, 30 September 2026) An enforced DMARC policy makes the first, simplest version of the attack, a forged From address on your exact domain, much harder.
Be honest about the limits. DMARC does not stop every attack. The same article points out that many business email compromise messages hijack real email threads or use a genuinely compromised account, and so pass SPF, DKIM and DMARC. DMARC closes one door, direct spoofing of your domain. You still need strong passwords, multi-factor authentication and a call-back habit before changing anyone's bank details.
Deliverability. Your own legitimate mail, such as tax pack reminders and engagement letters, is judged on the same records. A missing or inconsistent setup is one common reason a client says "I never got your email".
Your POPIA duty. Section 19 of the Protection of Personal Information Act is headed "Security measures on integrity and confidentiality of personal information" on the Information Regulator's knowledge base. (Information Regulator, Condition 7) It requires a responsible party to take appropriate and reasonable technical and organisational measures. We are not lawyers and nothing here is legal advice, but publishing a DMARC policy is a cheap, standard and easily explained technical measure that a firm handling client financial data can point to.
Your professional reputation. If a client receives a forged email in your firm's name, they will not care that you were not hacked. They will remember that the message looked like it came from you.
How to fix it, step by step
You do not need a developer for this. You need access to your domain's DNS settings (often with your domain registrar or web host) and to know which services send email as your firm. The example below uses the placeholder domain example.co.za. For more background, see our SPF, DKIM and DMARC guide for business email.
Step 1: List everything that sends email as you. That is usually your mailbox provider (Microsoft 365 or Google Workspace), your accounting or practice software, your invoicing tool, your newsletter tool and your website contact form. Anything missing from your SPF record will fail the check once enforcement starts.
Step 2: Publish one SPF record. There must be exactly one SPF record per domain. A Microsoft 365 example looks like this:
Type: TXT
Host: @ (example.co.za)
Value: v=spf1 include:spf.protection.outlook.com ~all
Add an include for each other sender, such as the value your invoicing tool gives you. Use the include value your provider documents. Google Workspace uses include:_spf.google.com.
Step 3: Turn on DKIM signing. In your mailbox provider's admin console, enable DKIM for example.co.za. It will give you one or two records to publish, usually CNAME records, for example:
Type: CNAME
Host: selector1._domainkey.example.co.za
Value: (the value your provider shows you)
Do the same for every other service that sends on your behalf.
Step 4: Publish DMARC in monitoring mode. Start with p=none and a mailbox that receives the reports:
Type: TXT
Host: _dmarc.example.co.za
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.co.za
Leave it for two to four weeks and read the reports. They show which services send as your domain and which pass.
Step 5: Fix any legitimate sender that fails, then tighten. Once every real sender passes, move to quarantine and then reject:
Value: v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-reports@example.co.za
Value: v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.co.za
The pct tag applies the policy to that percentage of failing mail while you gain confidence. The meaning of the three policy values is defined in the DMARC specification: none asks receivers to take no specific action, quarantine asks them to treat failing mail as suspicious, and reject asks them to refuse it. (RFC 7489, section 6.3, which the IETF has since marked as obsolete in favour of newer DMARC documents.)
Step 6: Check it. Send a test email to a Gmail address, open the message, and use "Show original" to see SPF, DKIM and DMARC all marked as pass. Repeat after any change to your email tools.
If your website or email is managed by someone else, forward them this list. If you also want the website side reviewed, our website for accountants guide covers what a professional practice site should include, and the accounting firm websites page explains how we build them.
Methodology
We built a list of 104 .co.za website domains belonging to South African accounting practices, auditors, tax practitioners, independent financial advisers, insurance brokers and fiduciary firms, using local search results across the main metros and several smaller towns, with directories and aggregators removed. On 9 November 2026 we ran passive checks: DNS lookups for MX, SPF (TXT containing v=spf1) and DMARC (TXT at _dmarc containing v=DMARC1, with the p= value read), plus one GET of each homepage and one GET of the http address, at roughly one request per second. We did not post forms, log in, scan ports or crawl beyond the homepage.
Limits you should know about:
- This is a convenience sample, not a random one. Firms that show up in local search are probably more web-aware than average, so the real picture is unlikely to be better.
- With about 100 domains, the margin of error on a percentage near 50 is roughly plus or minus 10 points.
- We checked that records exist and what DMARC policy they declare. We did not check DKIM (selectors cannot be discovered passively), report addresses, or whether each SPF record is correct.
- Banner and privacy-link detection works on raw homepage HTML and can miss items added by JavaScript.
- We do not name any firm. The anonymised per-row results are in the published data file, and this section documents the full method.
Dataset. The anonymised per-row results are published as a CSV file (104 rows, one per domain, no firm names) under a Creative Commons Attribution 4.0 licence (CC BY 4.0). Reuse it with credit to Next Level Web Solutions.
Sources
- Google, Email sender guidelines, checked 9 November 2026.
- Microsoft, Strengthening email ecosystem: Outlook's new requirements for high-volume senders, checked 9 November 2026.
- IETF, RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC).
- Information Regulator (South Africa), POPIA Condition 7: Security safeguards.
- ITWeb, Why the next fraud case against your business will start with an e-mail, 30 September 2026 (cites SABRIC's 2025 digital banking crime figures).
Check your own firm
Not sure where your firm stands? Our free website check looks at your site, and we are happy to point you at the email records that need fixing.
Cite this study: Next Level Web Solutions (2026). "We Checked 104 South African Accounting and Financial Firm Websites: 3 in 4 Can Have Their Email Spoofed." Published 9 November 2026. https://next-lvl.tech/blog/south-african-accounting-firms-email-security-study.html
Related reading
- Website for Accountants in South Africa: What to Include
What a website for accountants in South Africa should include: service pages, area pages, trust signals, an intake form that sorts enquiries and POPIA basics. (8 min read) - How to Get Clients as an Accountant in South Africa
How to get clients as an accountant or bookkeeper in South Africa: referrals, Google Business Profile, a niche, useful content and a site that sorts enquiries. (9 min read) - SEO for Accountants in South Africa: A Practical Guide
SEO for accountants and firms in South Africa: Google Business Profile, service and area pages, reviews, content on SARS and CIPC dates, and tracking. (9 min read)