[ Enterprise operations ]
Mail Check migration planning: verify official dates, scope and monitoring continuity
Use the official retirement scope and prove each replacement monitoring task works from input to action.
By the EmailAuth research team · 3 min read
[ Key points ]
- Treat the retirement as a past event, not a future deadline.
- Replace actual monitoring tasks and verify each stage.
- Keep missing historical evidence and unresolved continuity gaps explicit.
[ Takeaway ]
Keep missing historical evidence and unresolved continuity gaps explicit.
[ By role ]
What this means for you
Choose your role for practical next steps.
IT / Mail Admin
Test each monitoring stage
Configuration alone is incomplete.
Next steps
- Inspect report destinations
- Verify processing and alerts
- Record observation windows
CISO / SecOps
Keep the official scope precise
Retirement is not vendor endorsement.
Next steps
- Retain the dated notice
- Review unresolved visibility
- Separate claims from tests
Founder / Non-technical
Buy verified coverage
Procurement should follow required tasks.
Next steps
- List monitoring outcomes
- Request a scoped demonstration
- Assign a gap owner
[ FAQs ]
Frequently asked questions
Is 31 March 2026 still an upcoming deadline?
No. The official notice now describes Mail Check and Web Check as retired on that date.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
Did the notice also retire Early Warning?
No. It says subscribed Early Warning and DNS Check findings continue through MyNCSC.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
Does NCSC endorse my chosen replacement?
The notice recommends a product category and buying guidance, not your specific vendor.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
Does an old rua address prove reports are processed?
No. Check receipt, processing and operational use separately.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
Should moving reports weaken p=reject?
Not solely for a collector migration; treat policy changes as separate approved work.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
Must a replacement have one product dashboard?
No. Verify the required tasks even if several tools deliver them.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
What fails in the example?
The proposed test cases isolate an unavailable alert sink and missing input. These are expected outcomes to test, not executed results in this guide.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
What if historical exports are missing?
Document the gap and available evidence without inventing retrospective findings.
NCSC retirement of Mail Check and Web Check RFC 9990 DMARC aggregate reporting
[ Sources ]
Sources
- NCSC retirement of Mail Check and Web Check
Sections Retirement line36; scope45; category recommendation46–50
- RFC 9990 DMARC aggregate reporting
Sections §3,4,7,8
[ Glossary ]
Glossary
- EASM
- External attack surface management, a category of tools for identifying and assessing internet-facing assets.
- Continuity gate
- A set of required observations used to decide whether a replacement workflow works.
- Reporting destination
- The configured address or endpoint intended to receive a particular class of report.
Enterprise provenance
Why top financial institutions and governments retired their email security dashboards.
Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.
EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.
SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption