schedule 7-min read

What Does the NCSC Recommend for DMARC?

DMARC AI editorial team · Last updated

The NCSC recommends DMARC at p=reject on every domain, parked ones included. What its guidance says and what RFC 9989 and Mail Check’s end changed.

01

Introduction

The NCSC recommends that UK organisations publish DMARC on every domain they own and move to a policy of p=reject as soon as they are confident SPF and DKIM are working. Domains that send no email should be locked down with p=reject and an SPF record of v=spf1 -all straight away.

That advice sits in the NCSC's email security and anti-spoofing guidance, first published in 2019. Two things have changed since: the DMARC standard was replaced by RFC 9989 in May 2026, and the NCSC retired its free Mail Check service on 31 March 2026. This article sets out what the guidance says, which parts still apply as written, and how to follow it today. For the protocol itself, see the DMARC guide.

02

Key takeaways

  • The NCSC's end state is p=reject on all domains, plus secure email in transit.
  • Parked (non-sending) domains get v=spf1 -all and p=reject immediately.
  • The NCSC's 2019 example record stages enforcement with pct, a tag RFC 9989 removed; stage by policy level instead.
  • Mail Check was retired on 31 March 2026, so organisations and their MSPs need their own report processing.
  • No DMARC vendor is NCSC-approved, and DMARC is not a Cyber Essentials requirement.
03

What is the NCSC's DMARC implementation plan?

The NCSC recommends a phased approach with six steps: choose an anti-spoofing management tool, protect email in transit, configure anti-spoofing controls, send spoofed email to spam, reject spoofed email, and then improve continuously. The guidance gives no fixed durations, because the time needed depends on the organisation's size, complexity and resources.

The steps map directly onto DMARC policy levels:

NCSC step What it means in DMARC terms
Choose an anti-spoofing management tool Somewhere to receive and read aggregate (rua) reports
Configure anti-spoofing controls SPF, DKIM and a DMARC record at p=none with reporting
Send spoof emails to spam Move to p=quarantine
Reject spoof emails Move to p=reject
Continuous improvement Regular health checks and fixing what the reports show

The order matters more than the speed. Each move up is safe only when the reports show every legitimate sender passing, which is the same evidence gate described in how to move from DMARC monitoring to enforcement safely.

04

When does the NCSC say to move to p=reject?

The NCSC says to move to p=reject "as soon as you are confident DKIM and SPF are continuing to work correctly", and describes reject as the best way to prevent spoofing. It notes that many organisations move from quarantine to reject after about three months, advises monitoring reports for at least two weeks after the change, and says you can step back to quarantine if problems appear. Its reject guidance also uses sp=reject in its example, so subdomains are covered too.

05

Which parts of the NCSC guidance have dated?

One part has: the percentage ramp. The NCSC's example record sets a pct value of 50 and advises raising the percentage gradually to 100. RFC 9989 removed the pct tag (Appendix A.6), and receivers that implement the current standard ignore it. A record that still carries a percentage is treated as if the full policy applied to all failing mail.

To follow the NCSC's intent today, stage by policy level instead: p=none, then p=quarantine, then p=reject, each applied in full once the evidence supports it. If you want a rehearsal, RFC 9989 adds the t=y test mode, which asks receivers to apply the policy one level below the one you publish. The pct tag has been removed explains the change in detail.

06

What does the NCSC recommend for parked domains?

Domains that never send email should publish a reject policy and an SPF record that authorises nobody. The NCSC's guidance on parked domains gives these two records:

parkeddomain.example.     TXT  "v=spf1 -all"
_dmarc.parkeddomain.example. TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com"

Unlike sending domains, parked domains need no monitoring phase: there is no legitimate mail to break. For MSPs, this is the quickest win in any client estate, because most organisations own more registered domains than they send from. Should parked domains have a DMARC record? gives the full record set, including a null MX.

07

What happened to Mail Check?

The NCSC retired Mail Check and Web Check on 31 March 2026, as announced in its blog post of 6 November 2025. For organisations that relied on Mail Check to receive and summarise DMARC reports, that processing now has to happen elsewhere.

The NCSC's own suggestions are to adopt a commercial external attack surface management product, to subscribe to its Check your cyber security service, which checks an email domain for anti-spoofing and email privacy, and to keep using MyNCSC for findings from services such as Early Warning. None of these replaces daily processing of aggregate reports across many domains, which is the part an MSP has to provide. Replacing Mail Check-style monitoring covers the options for MSPs.

08

What applies to UK public sector domains?

Central government domains follow the GOV.UK email security standard, which builds on the NCSC guidance. It requires DMARC on inbound and outbound mail, a record that starts at p=none and moves to quarantine or reject, SPF with at least a soft fail (~all) qualifier, DKIM signing, and MTA-STS and TLS-RPT for transport security. Its example DMARC record sends aggregate reports to a central government address as well as the department's own mailbox; check the live page for the current reporting addresses, as services have changed since Mail Check's retirement. DMARC for UK public sector organisations covers the sector in more depth.

09

What the NCSC does not say

Two claims circulate that the guidance does not support. The NCSC does not approve or certify DMARC vendors, so treat any "NCSC-approved" label with suspicion. And DMARC is not a requirement of Cyber Essentials, even though it is good practice; see does Cyber Essentials require DMARC?. Nor does the UK Cyber Security and Resilience Bill name DMARC; it had not received Royal Assent as of 9 October 2026, and what it would mean for UK MSPs is set out separately.

10

How should an MSP apply the NCSC guidance?

Use the NCSC's six steps as the structure of a managed service and apply them per client domain:

  1. Inventory every domain, including parked ones, and lock parked domains down first.
  2. Collect reports centrally for all sending domains, with external destination verification if reports go to the MSP's domain (see DMARC aggregate reports explained).
  3. Name every sender in the reports and fix SPF and DKIM alignment per sender.
  4. Move each domain through quarantine to reject in full steps, with no pct, using t=y where a rehearsal helps.
  5. Keep watching after reject, which is the NCSC's continuous improvement step and the recurring part of the service.
11

FAQ

Does the NCSC require DMARC?

The NCSC recommends DMARC for all UK organisations; it is not a legal requirement for the private sector. Central government domains must follow the GOV.UK email security standard, which requires DMARC.

What DMARC policy does the NCSC recommend?

p=reject on every domain, reached once SPF and DKIM are confirmed to work. Parked domains should be set to p=reject immediately.

Can I still use pct as the NCSC example shows?

No. RFC 9989 removed pct in May 2026 and current receivers ignore it. Move between none, quarantine and reject in full steps instead.

What replaced Mail Check?

The NCSC did not launch a direct replacement. It points organisations to commercial tools and its Check your cyber security service; daily DMARC report processing now needs a DMARC platform or managed service.

Is any DMARC provider approved by the NCSC?

No. The NCSC does not approve DMARC vendors.

12

Final thoughts

The NCSC's DMARC advice has aged well in its goal and its order: report first, then quarantine, then reject, and lock parked domains down at once. Only the mechanics need updating for 2026. Stage by policy level rather than percentage, and plan who processes the reports now that Mail Check has gone.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.