Mail Check has closed: what councils should do now
For years, many councils and other public bodies relied on the NCSC's Mail Check service. It checked their email domains against the government standard and processed their DMARC reports. The NCSC retired it on 31 March 2026 [1]. The standard itself hasn't gone anywhere, though. This guide sets out what is still required, what Mail Check's closure changes, and a practical order of work.
The standard still applies
The GOV.UK guidance on securing government email covers every email domain that public sector organisations run on the internet [2]. Under that guidance, you must:
- support TLS 1.2 or later for sending and receiving, and publish an MTA-STS policy for every domain that receives email
- have DMARC, DKIM and SPF records in place, so your domains are hard to spoof
- filter spam and malware, and enforce DMARC on the email you receive
- set up DMARC and TLS reporting, and review the reports regularly
- give every sending service a valid PTR (reverse DNS) record [2]
The companion set-up guide adds detail. DMARC should start at p=none and move up to quarantine or reject during implementation. SPF should list every system that sends your mail and end in at least a soft fail (~all). MTA-STS should start in testing mode and move to enforce soon after, or it has no effect [3].
Domains that never send email need protecting too. The guidance asks for an SPF record that allows no senders, a DMARC record set to reject, an empty DKIM record and, where your DNS host supports it, a null MX record [4].
What Mail Check's closure changes
Mail Check closed in two steps. The NCSC stopped providing DMARC aggregate reports, DMARC Insights, the related DKIM checks and TLS reporting on 24 March 2025 [5]. The scanning of DMARC, SPF, MTA-STS and inbound TLS ended with the full retirement on 31 March 2026 [1][5].
The GOV.UK pages haven't caught up yet. They still advise signing up to Mail Check to process your DMARC and TLS reports [2]. The example records in the set-up guide still send TLS reports to a Mail Check address and DMARC reports to an address at dmarc.service.gov.uk [3]. The page for non-sending domains still tells you to confirm your settings in Mail Check [4]. If your records were copied from those examples, your reports still go to Mail Check, and no one at Mail Check has read those reports for over 18 months.
Your obligation to "review the data regularly" [2] hasn't changed. You now need your own way of meeting it.
What the NCSC suggests
The NCSC recommends two things: a commercial external attack surface management (EASM) product, and subscribing to its free Check your cyber security service, which checks a domain for email anti-spoofing and email privacy [1][6]. The NCSC's EASM buyer's guide lists email security checks, such as SPF, DMARC and MTA-STS, among the features to look for. It also includes "ensuring email anti-spoofing controls are deployed" as a typical goal [7]. For public sector buyers, the NCSC points to DMARC tools on the GOV.UK Digital Marketplace [5].
A practical order of work
- List every domain you own. That includes old service domains, campaign sites and defensive registrations that never send mail. Apply the non-sending domain records to anything that doesn't send email [4].
- Find the reporting addresses. Check the
rua=tag in each DMARC record and the_smtp._tlsrecord. Replace any Mail Check orservice.gov.ukreporting address with one you control or a service you have chosen. Change only the address. Leave your DMARC policy exactly as it is. - Choose how reports will be read. You can use a paid platform, the reporting tool your email provider includes, or an open-source parser run on your own systems. Choose based on how many domains you run and who will act on the findings [7].
- Close the gaps against the standard. Most councils have already done the hardest part, which is DMARC enforcement. The next items are usually MTA-STS in
enforcemode, TLS-RPT and the non-sending domains [3][4]. - Re-check regularly. DNS changes when suppliers change. Put a quarterly check in the diary, or let a monitoring tool alert you.
How councils compare
On 8 November 2026, FaultyPacket read the public DMARC records of 376 UK council email domains [8]. Of these:
- 228 (60.6%) published
p=reject - 131 (34.8%) published
p=quarantine - 15 (4.0%) had
p=noneor no record, so fake email using their domain would be delivered as normal
The remaining two domains applied quarantine to only part of their failing mail [8]. The study names no councils, and it doesn't claim that any council has been impersonated or is non-compliant [8]. It does show that DMARC enforcement is already normal practice. The gaps that remain are reporting, MTA-STS and the domains people forget.
A note on what DMARC doesn't do
DMARC stops criminals sending email as your exact domain. It doesn't stop look-alike domains, and it doesn't help once a real mailbox has been taken over. Staff and supplier awareness still matter, and so does MFA on every mailbox.
Check your domain free
You can check any council or public body domain for free at faultypacket.co.uk. It reads your public SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and CAA records and explains each finding in plain English. If something needs fixing, the £24 Fix Pack gives you the exact records to add, in a safe order, and re-checks each one live once you've added it.
DNS on Cloudflare? Fix it for me adds your SPF and DMARC records in one click (£49 plus VAT, Fix Pack included). To hear if anything changes later, monitoring checks your domain every day from £4 a month.
Sources
- NCSC, "NCSC to retire Web Check and Mail Check" (updated 24 Aug 2026): https://www.ncsc.gov.uk/blog-post/retiring-mail-check-web-check
- GDS and CDDO, "Securing government email" (updated 4 Mar 2024): https://www.gov.uk/guidance/securing-government-email
- GDS and CDDO, "Set up government email services securely" (updated 4 Mar 2024): https://www.gov.uk/guidance/set-up-government-email-services-securely
- GDS and CDDO, "Protect domains that do not send email" (updated 1 Mar 2021): https://www.gov.uk/guidance/protect-domains-that-dont-send-email
- NCSC, "Mail Check update" (PDF, 14 Nov 2024): https://www.ncsc.gov.uk/sites/default/files/2026-08/Mail-Check-update.pdf
- NCSC, Check your email security: https://checkcybersecurity.service.ncsc.gov.uk/email-security-check/
- NCSC, EASM buyer's guide (18 Sep 2025): https://www.ncsc.gov.uk/guidance/external-attack-surface-management-buyers-guide
- FaultyPacket, "Could someone fake your council's email?" (snapshot 8 Nov 2026): https://faultypacket.co.uk/research/council-email-spoofing