Domain and email security cleanup for a South African SME

Overview

The client was a South African professional services business that relied on email for client communication, quotes, invoices, approvals, and internal operations.

The business used Microsoft 365, but its DNS and email authentication records had grown over time. Different systems had been added, changed, or removed, and the domain no longer had a clean, easy-to-understand email security picture.

The concern was practical: reduce spoofing risk, improve trust in the domain, and understand which systems were actually allowed to send email.

The challenge

The domain worked, but it was not clean. That is a common SME problem. Email keeps flowing, so risky DNS records can sit unnoticed for years.

The main risks were old SPF entries, DKIM that needed validation, weak or missing DMARC, no useful DMARC reporting, old DNS records, unclear mail flow, external sending services that were not fully understood, and limited visibility into spoofing attempts.

The business needed a cleanup that improved security without disrupting daily email.

What ITried reviewed

ITried reviewed the domain and email setup from public DNS through to Microsoft 365 mail flow. The goal was to understand what existed, what was still needed, what was risky, and what could be improved safely.

• DNS records and old published entries
• SPF alignment and unnecessary includes
• DKIM setup or validation
• DMARC setup, policy, and reporting
• MX records and Microsoft 365 mail flow
• External services sending email for the domain
• SSL certificate status
• Domain expiry, WHOIS, and registrar details
• MTA-STS and TLS-RPT readiness
• Common email authentication gaps
• Documentation of the current setup and remediation list

ITried also explained which systems were allowed to send email for the domain. That helped the client understand what belonged in DNS and what needed to be removed or corrected.

The outcome

The client gained a cleaner domain and email security setup. SPF became easier to understand, DKIM was validated, DMARC reporting improved visibility, and old DNS records were identified.

Microsoft 365 mail flow became clearer, and the business had a better way to monitor domain misuse and email authentication issues.

The result was a safer email foundation for Microsoft 365 and business communication.

Why this mattered

Email is one of the highest-risk systems in an SME. A weak domain setup makes it easier for attackers to impersonate the business. Poor DNS records also create delivery issues and confusion when websites, CRMs, accounting systems, marketing tools, or suppliers send email.

A domain and email security cleanup helps protect trust in the business name. It also gives the business better visibility into who is sending email on behalf of its domain.

Best fit for this check

This kind of review is useful for SMEs using Microsoft 365, businesses sending quotes or invoices by email, companies with multiple email sending platforms, and teams dealing with spoofing, phishing, old DNS records, or mail delivery problems.

It is also useful before or after moving email to Microsoft 365, adding a CRM, adding accounting email, changing website platforms, or preparing for broader Microsoft 365 security improvements.

FAQ