DMARC, DKIM, and SPF are the three DNS records that determine whether your email is trustworthy. We configure and enforce all three — and prevent spoofing of your domain.
Delivered by senior engineers. Scoped and priced upfront. No scope surprises.
Policy progression from p=none through p=quarantine to p=reject enforcement. Ongoing DMARC aggregate report analysis and remediation of legitimate sending sources.
SPF audit and rebuild for all authorised sending sources. DKIM key rotation, selector configuration, and alignment verification across Exchange Online and third-party senders.
Proofpoint Essentials or Defender for Office 365 Plan 2 deployment. Anti-phishing, safe links, safe attachments, and impersonation protection configured.
Investigation of deliverability issues including IP reputation, blacklist removal, bounce rate reduction, and bulk mail compliance.
Audit of all services sending on your domain — CRM, marketing, ticketing — and correct SPF and DKIM alignment for each.
Monthly DMARC aggregate report review with alerts for new unauthorised sending sources. Forensic report configuration.
Select your role to see how this service maps to your specific situation.
Your email looks fine from your side. But recipients may be receiving it in junk. Or attackers may be sending invoices, payment instructions, and credential requests from your domain — and your clients have no technical way to tell the difference. DMARC enforcement at p=reject means only authorised senders can successfully deliver email from your domain.
Security management means more than having a firewall. DMARC aggregate reporting gives you a daily view of every mail server sending on behalf of your domain — including ones you didn't authorise. SPF and DKIM alignment tells you whether your legitimate senders are passing authentication. Without this visibility, you are flying blind.
The most common fraud scenario we see: a supplier's email domain is spoofed, an invoice is sent to your accounts team from what appears to be a legitimate address, and payment is made. The supplier never sent it. DMARC enforcement on both your domain and your key suppliers' domains is the primary technical control against this attack pattern.
DMARC at p=reject or p=quarantine is specified in NIS2 technical implementation guidance and in most public sector email security requirements as a mandatory anti-spoofing control. Beyond compliance, a domain that can be spoofed represents a reputational and liability risk that procurement assessors are increasingly aware of and will flag in a security review.
These are not edge cases. They are the standard state of an SME environment without an independent review.
Domain spoofable by anyone. p=none monitors but does not block. Most organisations have been at this stage for years with no progression.
Records exceeding the 10-lookup DNS limit, deprecated PTR mechanisms, or missing includes for third-party senders causing legitimate mail to fail.
Exchange Online default filtering is insufficient for targeted phishing and business email compromise. Defender for O365 Plan 2 or Proofpoint required.
Four stages. No handovers to junior staff mid-project. No scope surprises.
DNS record review for SPF, DKIM, and DMARC. Deliverability test across major inbox providers. Third-party sender inventory.
SPF rebuilt for all authorised sources. DKIM keys generated and published. DMARC at p=none with RUA and RUF reporting configured.
Aggregate report analysis to identify all legitimate sending sources. Systematic progression to p=quarantine then p=reject over 2-4 weeks.
Monthly DMARC report review. Alerts for new unauthorised senders. Annual deliverability audit and DKIM key rotation.
Share your domain name and we will run an immediate DMARC, SPF, and DKIM check before we speak. No commitment required.
Tell us your domain name and we can run an immediate DMARC and SPF check before the call.
No commitment required.
No commitment is required at this stage.