Skip to content
The STARK NEXUS Technology. Systems. Solutions.
Cybersecurity

Email authentication is no longer optional for Kenyan businesses

SPF, DKIM and DMARC are the difference between a spoofed invoice landing in a client inbox and being rejected at the gateway.

N

The Stark Nexus

10 November 2026 · 2 min read

Business email compromise rarely starts with sophisticated malware. More often it starts with a message that looks like it came from a supplier, a director, or your own domain.

What the three records actually do

SPF lists the servers allowed to send mail for your domain. DKIM cryptographically signs outgoing messages so receivers can verify they were not altered. DMARC tells receiving servers what to do when a message fails those checks, and sends you reports about attempts to use your domain.

Why partial configuration is worse than none

A published SPF record without DKIM alignment, or a DMARC policy still set to p=none, gives the appearance of protection without enforcement. Most organisations stay at monitoring for months because nobody owns the reporting inbox.

A practical sequence

  1. Inventory every system that sends mail on your behalf, including ticketing tools and CRMs.
  2. Publish SPF and DKIM for each sending source.
  3. Start DMARC at p=none and read the aggregate reports.
  4. Move to quarantine, then reject, once legitimate sources are aligned.
  5. Monitor continuously — new tools break alignment quietly.
Authentication prevents impersonation of your domain. It does not stop a compromised mailbox, which is why MFA and mailbox monitoring still matter.

Where to start

If you cannot say which servers are authorised to send mail for your domain today, that is the first gap to close. The work is measurable: fewer spoofed messages, cleaner deliverability, and evidence for clients who ask how you protect their data.

Filed under #Security

Share this article

Useful for a colleague or a board paper?